linux-kernel - Re: BKL use in ptrace

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] [day] [month] [year] [list]

Message-Id: <20091222011329.D78C010274@magilla.sf.frob.com>
Date:	Mon, 21 Dec 2009 17:13:29 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: BKL use in ptrace

> I never understood this lock_kernel().
> 
> In any case it looks outdated. We were going to kill it "soon",
> along with other ptrace changes.

I never understood it either.  It's very ancient and long predates many,
many ptrace cleanups.  If the comment was ever accurate, then any issue
like that is now covered by cred_guard_mutex.  I don't know of any reason
for (or really, effect of) using BKL in ptrace.


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/