[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87educb7rm.fsf@suse.de>
Date: Wed, 09 Nov 2022 14:02:37 +0100
From: Nicolai Stange <nstange@...e.de>
To: Daniel Jordan <daniel.m.jordan@...cle.com>
Cc: Nicolai Stange <nstange@...e.de>,
Steffen Klassert <steffen.klassert@...unet.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Martin Doucha <mdoucha@...e.cz>, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] padata: make padata_free_shell() to respect pd's
->refcnt
Daniel Jordan <daniel.m.jordan@...cle.com> writes:
> On Wed, Oct 19, 2022 at 10:37:05AM +0200, Nicolai Stange wrote:
>>
>> Fixes: 07928d9bfc81 ("padata: Remove broken queue flushing")
>
> It looks like this issue goes back to the first padata commit. For
> instance, pd->refcnt goes to zero after the last _priv is serialized,
> padata_free is called in another task, and a particularly sluggish
> padata_reorder call touches pd after.
>
> So wouldn't it be
>
> Fixes: 16295bec6398 ("padata: Generic parallelization/serialization interface")
I chose 07928d9bfc81 ("padata: Remove broken queue flushing"), because
that one reads like it fixed a couple of much more severe padata
lifetime issues, it only missed the relatively minor one addressed here,
in a sense.
Or to put it the other way around: if one were to backport this patch
here, 07928d9bfc81 should probably get picked first, I think.
But I'd be fine with any Fixes tag, of course, I don't have a strong
opinion on this matter.
Thanks!
Nicolai
>
> ?
>
> Otherwise,
>
> Acked-by: Daniel Jordan <daniel.m.jordan@...cle.com>
>
>> Signed-off-by: Nicolai Stange <nstange@...e.de>
>> ---
--
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
(HRB 36809, AG Nürnberg)
Powered by blists - more mailing lists