aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorIngo Molnar <[email protected]>2008-11-27 13:41:21 +0000
committerIngo Molnar <[email protected]>2008-11-28 14:01:46 +0000
commit5b3eec0c80038c8739ccd465b897a35c0dff1cc4 (patch)
tree52a4625c34af62dc41233ecdf21e2d5262683e8f /net/unix/af_unix.c
parentMerge branch 'x86/debug' into x86/irq (diff)
downloadkernel-5b3eec0c80038c8739ccd465b897a35c0dff1cc4.tar.gz
kernel-5b3eec0c80038c8739ccd465b897a35c0dff1cc4.zip
x86: ret_from_fork - get rid of jump back
Impact: remove dead code If we take a closer look at the rff_trace/rff_action ret_from_fork code, we have to realize that it does all the wrong things: for example it checks the TIF flag - while later on jumping back to the ret-from-syscall path - duplicating the check needlessly. But checking for _TIF_SYSCALL_TRACE is completely unnecessary here because we clear that flag for every freshly forked task. So the whole "tracing" code here, for which there is a out of line jump optimization that makes it even harder to read, is in reality completely dead code ... Reported-by: Cyrill Gorcunov <[email protected]> Signed-off-by: Ingo Molnar <[email protected]> Tested-by: Cyrill Gorcunov <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions