[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZEaCSXG4UTGlHDam@casper.infradead.org>
Date: Mon, 24 Apr 2023 14:21:13 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: syzbot <syzbot+606f94dfeaaa45124c90@...kaller.appspotmail.com>,
djwong@...nel.org, hch@...radead.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-xfs@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [fs?] [mm?] KCSAN: data-race in __filemap_remove_folio
/ folio_mapping (2)
On Mon, Apr 24, 2023 at 09:38:43AM +0200, Dmitry Vyukov wrote:
> On Mon, 24 Apr 2023 at 09:19, syzbot
> <syzbot+606f94dfeaaa45124c90@...kaller.appspotmail.com> wrote:
> If I am reading this correctly, it can lead to NULL derefs in
> folio_mapping() if folio->mapping is read twice. I think
> folio->mapping reads/writes need to use READ/WRITE_ONCE if racy.
You aren't reading it correctly.
mapping = folio->mapping;
if ((unsigned long)mapping & PAGE_MAPPING_FLAGS)
return NULL;
return mapping;
The racing write is storing NULL. So it might return NULL or it might
return the old mapping, or it might return NULL. Either way, the caller
has to be prepared for NULL to be returned.
It's a false posiive, but probably worth silencing with a READ_ONCE().
Powered by blists - more mailing lists