[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200428171420.045f0acc9e1bf20044c4560e@linux-foundation.org>
Date: Tue, 28 Apr 2020 17:14:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Wei Yongjun <weiyongjun1@...wei.com>,
Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@...el.com>,
Waiman Long <longman@...hat.com>,
Manfred Spraul <manfred@...orfullife.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Alexey Dobriyan <adobriyan@...il.com>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH -next] ipc: use GFP_ATOMIC under spin lock
On Tue, 28 Apr 2020 04:14:03 -0700 Matthew Wilcox <willy@...radead.org> wrote:
> On Tue, Apr 28, 2020 at 03:47:36AM +0000, Wei Yongjun wrote:
> > The function ipc_id_alloc() is called from ipc_addid(), in which
> > a spin lock is held, so we should use GFP_ATOMIC instead.
> >
> > Fixes: de5738d1c364 ("ipc: convert ipcs_idr to XArray")
> > Signed-off-by: Wei Yongjun <weiyongjun1@...wei.com>
>
> I see why you think that, but it's not true. Yes, we hold a spinlock, but
> the spinlock is in an object which is not reachable from any other CPU.
> So it's not possible to deadlock.
um, then why are we taking it?
> This probably confuses all kinds
> of automated checkers,
A big fat code comment would reduce the email traffic?
> and I should probably rewrite the code to not
> acquire the new spinlock until we're already holding the xa_lock.
>
Powered by blists - more mailing lists