[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPAsAGxPEZYBCb30=an8yyku9zNZT74g3n4W_XFCRwLgg=9Xyw@mail.gmail.com>
Date: Thu, 18 Apr 2024 15:58:52 +0200
From: Andrey Ryabinin <ryabinin.a.a@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Dave Chinner <david@...morbit.com>, Xiubo Li <xiubli@...hat.com>, linux-xfs@...r.kernel.org,
chandan.babu@...cle.com, djwong@...nel.org, linux-kernel@...r.kernel.org,
kasan-dev@...glegroups.com
Subject: Re: xfs : WARNING: possible circular locking dependency detected
On Thu, Apr 18, 2024 at 8:56 AM Christoph Hellwig <hch@...radead.org> wrote:
>
> Adding the KASAN maintainer so that we actuall have a chane of
> fixing this instead of a rant that just gets lost on the xfs list..
>
Thanks.
> On Thu, Apr 18, 2024 at 03:04:24PM +1000, Dave Chinner wrote:
> > The only krealloc() in this path is:
> >
> > new = krealloc(ifp->if_data, new_size,
> > GFP_KERNEL | __GFP_NOLOCKDEP | __GFP_NOFAIL);
> >
> > And it explicitly uses __GFP_NOLOCKDEP to tell lockdep not to warn
> > about this allocation because of this false positive situation.
> >
> > Oh. I've seen this before. This is a KASAN bug, and I'm pretty sure
> > I've posted a patch to fix it a fair while back that nobody seemed
> > to care about enough to review or merge it.
> >
Sorry, must have been my bad. I didn't find the actual patch though,
only proposed way to fix this bug:
https://lkml.kernel.org/r/%3C20230119045253.GI360264@dread.disaster.area%3E
So I'll cook patch and will send it shortly.
Powered by blists - more mailing lists