[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <i2slhi24qpy4u4mtb7edm3sqqcazjfiw52xnz44i4o3vrhvoqe@d2qy423tdjly>
Date: Mon, 19 Jan 2026 02:20:11 -0800
From: Breno Leitao <leitao@...ian.org>
To: Marco Elver <elver@...gle.com>, akpm@...ux-foundation.org
Cc: Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>,
kasan-dev@...glegroups.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org, clm@...a.com,
kernel-team@...a.com
Subject: Re: [PATCH] mm/kfence: fix potential deadlock in reboot notifier
Hello Marco, Andrew,
On Mon, Jan 19, 2026 at 08:00:00AM +0100, Marco Elver wrote:
> On Fri, 16 Jan 2026 at 16:49, Breno Leitao <leitao@...ian.org> wrote:
>
> > The issue is that cancel_delayed_work_sync() waits for the work to
> > complete, but the work is waiting for kfence_allocation_gate > 0
> > which requires allocations to happen (each allocation is increated by 1)
>
> increated -> increased
[...]
> Reviewed-by: Marco Elver <elver@...gle.com>
Thanks for reviewing this patch.
Andrew,
Please let me know if you want to send me a v2 with the typo above
fixed, or, if you can fix it in your own tree.
Thanks
--breno
Powered by blists - more mailing lists