lkml.org 
[lkml]   [1999]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Bug: Tracing recursive system calls
Date
From
> syscall_trace is in the fast path?!?  It only gets called when a process
> is being traced, and nobody expects traced processes to run extremely
> fast, do they?

Fast path for tracing syscalls. It would be nice to avoid a check every
trace is what I mean.

> The problem isn't that the child thread is traced, it's that the `clone'
> call itself from `kernel_thread' is traced. So one would have to clear
> the flag and then reset it in the parent.

Ok

> Besides, this doesn't suffice. There are other places in the kernel
> that make system calls (there's a `waitpid' in `request_module' for
> instance). We would need to find and change all of these and institute
> a rule for the future, or else change the inline asm definitions in
> asm/unistd.h. Either seems a lot more complex.

Good point. My solution is simple elegant and wrong.

Alan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.047 / U:0.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site