linux-kernel - Re: [patch-RFC 00/26] LTTng Kernel Trace Thread Flag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <y0mmysnzf2q.fsf@ton.toronto.redhat.com>
Date:	Thu, 06 Dec 2007 16:30:21 -0500
From:	fche@...hat.com (Frank Ch. Eigler)
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch-RFC 00/26] LTTng Kernel Trace Thread Flag

Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> writes:

> This is an RFC for addition of a new thread flag, TIF_KERNEL_TRACE, to each
> architecture to activate system-wide system call tracing.
> [...]

Instead of creating a new flag, could you overload TIF_SYSCALL_TRACE,
putting the marker into syscall_trace(), and letting !PT_TRACED cause
a skip over the ptrace notification logic?

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