[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250206-pfirsich-fortbestand-fd0fa94edde8@brauner>
Date: Thu, 6 Feb 2025 11:40:19 +0100
From: Christian Brauner <brauner@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Mateusz Guzik <mjguzik@...il.com>, ebiederm@...ssion.com,
akpm@...ux-foundation.org, Liam.Howlett@...cle.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 1/5] exit: perform add_device_randomness() without
tasklist_lock
On Wed, Feb 05, 2025 at 09:56:56PM +0100, Oleg Nesterov wrote:
> On 02/05, Mateusz Guzik wrote:
> >
> > Parallel calls to add_device_randomness() contend on their own.
> ...
> > + add_device_randomness(&p->se.sum_exec_runtime,
> > + sizeof(p->se.sum_exec_runtime));
>
> OK, but
>
> > + free_pids(post.pids);
>
> wait... free_pids() comes later in 4/5 ?
Yes, that seems to be an accidental leftover. A
git rebase -S -i v6.14-rc1 -x "make -j7 O=build.v1/ kernel/"
caught this right away. Removed.
Powered by blists - more mailing lists