lkml.org 
[lkml]   [2009]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 08/12] add trace events for each syscall entry/exit

    On Wed, 26 Aug 2009, Frederic Weisbecker wrote:
    > >
    > > Oh yes, you are right. kernel threads created with kernel_thread()
    > > have t->mm != NULL if the forking process has an mm too.
    > >
    > > There are very few callsites left which still use kernel_thread().
    > > (the last one in s390 driver code will be gone after the next
    > > merge window).
    > >
    > > As far as I can there are only four callsites left
    > > (excluding staging): jffs2 and three in net/bluetooth/*
    >
    >
    > In that case, I'd suggest to pick the patch that checks for
    > kernel threads while setting the TIF_FLAGS.
    >
    > The check for invalid syscall numbers in another patch should be
    > sufficient to not crash.
    >
    > We might have rare inaccurate result because of the remaining
    > buggy callsites but instead of working around on it, these
    > should be fixed.

    Well, do these (buggy threads) call syscalls?

    -- Steve



    \
     
     \ /
      Last update: 2009-08-26 16:45    [W:2.594 / U:0.760 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site