linux-kernel - Re: [PATCH 2/2] getrusage: use sig->stats

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: <20240121143218.35d3171018771e5c2b5820e3@linux-foundation.org>
Date: Sun, 21 Jan 2024 14:32:18 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dylan Hatch <dylanbhatch@...gle.com>
Cc: Oleg Nesterov <oleg@...hat.com>, Kees Cook <keescook@...omium.org>,
 Frederic Weisbecker <frederic@...nel.org>, "Joel Fernandes (Google)"
 <joel@...lfernandes.org>, Ard Biesheuvel <ardb@...nel.org>,
 "Matthew Wilcox (Oracle)" <willy@...radead.org>, Thomas Gleixner
 <tglx@...utronix.de>, Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
 "Eric W. Biederman" <ebiederm@...ssion.com>, Vincent Whitchurch
 <vincent.whitchurch@...s.com>, Dmitry Vyukov <dvyukov@...gle.com>, Luis
 Chamberlain <mcgrof@...nel.org>, Mike Christie
 <michael.christie@...cle.com>, David Hildenbrand <david@...hat.com>,
 Catalin Marinas <catalin.marinas@....com>, Stefan Roesch
 <shr@...kernel.io>, Joey Gouly <joey.gouly@....com>, Josh Triplett
 <josh@...htriplett.org>, Helge Deller <deller@....de>, Ondrej Mosnacek
 <omosnace@...hat.com>, Florent Revest <revest@...omium.org>, Miguel Ojeda
 <ojeda@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] getrusage: use sig->stats_lock

On Fri, 19 Jan 2024 19:27:49 -0800 Dylan Hatch <dylanbhatch@...gle.com> wrote:

> 
> I applied these to a 5.10 kernel, and my repro (calling getrusage(RUSAGE_SELF)
> from 200K threads) is no longer triggering a hard lockup.

Thanks, but...

The changelogs don't actually describe any hard lockup.  [1/2] does
mention "the deadlock" but that's all the info we have.

So could we please have a suitable description of the bug which these are
addressing?  And a Reported-by:, a Closes: and a Fixes would be great too.