linux-kernel - Re: [PATCH] coredump: Do not lock during 'comm' reporting

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: <20240928143532.39559729f9eceee468358abe@linux-foundation.org>
Date: Sat, 28 Sep 2024 14:35:32 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kees Cook <kees@...nel.org>
Cc: Vegard Nossum <vegard.nossum@...cle.com>, "Eric W. Biederman"
 <ebiederm@...ssion.com>, Allen Pais <apais@...ux.microsoft.com>, Roman
 Kisel <romank@...ux.microsoft.com>, Xiaoming Ni <nixiaoming@...wei.com>,
 Vijay Nag <nagvijay@...rosoft.com>, linux-kernel@...r.kernel.org,
 linux-hardening@...r.kernel.org
Subject: Re: [PATCH] coredump: Do not lock during 'comm' reporting

On Sat, 28 Sep 2024 14:08:31 -0700 Kees Cook <kees@...nel.org> wrote:

> The 'comm' member will always be NUL terminated,

Why is this?  I thought this is only true if the caller holds task_lock()?

> and this is not
> fast-path, so we can just perform a direct memcpy during a coredump
> instead of potentially deadlocking while holding the task struct lock.
>