[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230703083938.CEkQ9Nhd@linutronix.de>
Date: Mon, 3 Jul 2023 10:39:38 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Michal Hocko <mhocko@...e.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, pmladek@...e.com,
will@...nel.org, tglx@...utronix.de, peterz@...radead.org,
mingo@...hat.com, mgorman@...hsingularity.net, longman@...hat.com,
lgoncalv@...hat.com, john.ogness@...utronix.de, david@...hat.com,
boqun.feng@...il.com, mm-commits@...r.kernel.org
Subject: Re: +
mm-page_alloc-use-write_seqlock_irqsave-instead-write_seqlock-local_irq_save.patch
added to mm-unstable branch
On 2023-07-03 10:00:47 [+0200], Michal Hocko wrote:
> On Mon 03-07-23 09:09:46, Tetsuo Handa wrote:
> > Nacked-by: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
> >
> > because of https://lkml.kernel.org/r/a1c559b7-335e-5401-d167-301c5b1cd312@I-love.SAKURA.ne.jp .
>
> This is not really productive approach! You are rising non-material
> concerns you haven't proven to be real. This is blocking otherwise
> useful fix. I am completely fine recording your nack with a reference to
> your concern should we ever trip over your concerns and so we can easily
> revert and find a different solution but I do not believe this should
> stand in the way in the fix.
>
> Now concerning the patch 1 in the series, I do agree this should be
> passing through the lockdep maintainers. But this fix is not really
> dependent on it.
I fully agree here.
Sebastian
Powered by blists - more mailing lists