linux-kernel - Re: [RFC patch 00/20] Kernel tracing 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]

Date:	Sun, 10 May 2009 16:04:35 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [RFC patch 00/20] Kernel tracing thread flag

I suspect you will hit troubles with some arch's not having a bit to spare.
(Even on x86, it probably hurts several bytes of cache wastage to have to
use longer immediates in some 'test' instructions.)

Another direction to go for this is overloading TIF_SYSCALL_TRACE, so we do
not need any arch changes.  Before the end of the ptrace cleanup work that
Oleg is in the middle of, it should become simple to divorce ptrace's own
bookkeeping from TIF_SYSCALL_TRACE.  At that point, we just need a little
bit of cooperation (in generic non-arch code) to overload that bit for
multiple simultaneous purposes.

Thanks,
Roland
--
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/