linux-kernel - Re: [PATCH] yama: don't abuse rcu_read_lock/get_task_struct in yama_task

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: <174113238769.4011875.8051227227833188142.b4-ty@kernel.org>
Date: Tue,  4 Mar 2025 15:53:08 -0800
From: Kees Cook <kees@...nel.org>
To: Paul Moore <paul@...l-moore.com>,
	James Morris <jmorris@...ei.org>,
	"Serge E. Hallyn" <serge@...lyn.com>,
	Oleg Nesterov <oleg@...hat.com>
Cc: Kees Cook <kees@...nel.org>,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] yama: don't abuse rcu_read_lock/get_task_struct in yama_task_prctl()

On Wed, 19 Feb 2025 17:14:17 +0100, Oleg Nesterov wrote:
> current->group_leader is stable, no need to take rcu_read_lock() and do
> get/put_task_struct().
> 
> 

Applied to for-next/hardening, thanks!

[1/1] yama: don't abuse rcu_read_lock/get_task_struct in yama_task_prctl()
      https://git.kernel.org/kees/c/c6822ed5d037

Take care,

-- 
Kees Cook