linux-kernel - Re: remove PT_DTRACE from arch/* except arch/um

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: <20090423063613.278E8FC3C7@magilla.sf.frob.com>
Date:	Wed, 22 Apr 2009 23:36:13 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: remove PT_DTRACE from arch/* except arch/um

> Unfortunately, I know nothing about these arches, so I can only rely on grep.
> But it really looks like nobody except arch/um actually uses DTRACE.

Same with me.  But I do trust grep, and my knowledge that PT_DTRACE was
widely used old cruft.  To be really paranoid, you can grep (painfully)
for all ->ptrace ('[>.]ptrace\>') in arch code, plus find any that use
it in asm-offsets.c, and then grep for TSK_PTRACE or whatever macro is
defined there.  (Chances are high that there are no uses that you missed.)
Or you could just leave it to the arch people to pipe up if we're wrong.

The patches all look quite right and harmless to me.

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/