Received-SPF: pass (google.com: domain of linux-kernel+bounces-32210-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Sun, 21 Jan 2024 14:32:18 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Dylan Hatch <dylanbhatch@google.com>
Cc: Oleg Nesterov <oleg@redhat.com>, Kees Cook <keescook@chromium.org>,
 Frederic Weisbecker <frederic@kernel.org>, "Joel Fernandes (Google)"
 <joel@joelfernandes.org>, Ard Biesheuvel <ardb@kernel.org>,
 "Matthew Wilcox (Oracle)" <willy@infradead.org>, Thomas Gleixner
 <tglx@linutronix.de>, Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
 "Eric W. Biederman" <ebiederm@xmission.com>, Vincent Whitchurch
 <vincent.whitchurch@axis.com>, Dmitry Vyukov <dvyukov@google.com>, Luis
 Chamberlain <mcgrof@kernel.org>, Mike Christie
 <michael.christie@oracle.com>, David Hildenbrand <david@redhat.com>,
 Catalin Marinas <catalin.marinas@arm.com>, Stefan Roesch
 <shr@devkernel.io>, Joey Gouly <joey.gouly@arm.com>, Josh Triplett
 <josh@joshtriplett.org>, Helge Deller <deller@gmx.de>, Ondrej Mosnacek
 <omosnace@redhat.com>, Florent Revest <revest@chromium.org>, Miguel Ojeda
 <ojeda@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] getrusage: use sig->stats_lock
Message-Id: <20240121143218.35d3171018771e5c2b5820e3@linux-foundation.org>
In-Reply-To: <CADBMgpxC+BP-wfrM-wP1nbZOcRb0LbsmMDQ3LQ8hUKYsF3QECw@mail.gmail.com>
References: <20240117192534.1327608-1-dylanbhatch@google.com>
	<20240119141501.GA23739@redhat.com>
	<20240119141529.GB23739@redhat.com>
	<CADBMgpxC+BP-wfrM-wP1nbZOcRb0LbsmMDQ3LQ8hUKYsF3QECw@mail.gmail.com>
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 19 Jan 2024 19:27:49 -0800 Dylan Hatch <dylanbhatch@google.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.