From: "Darrick J. Wong" <djwong@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [6.15-rc2 regression] iomap: null pointer in a bio completion
Date: Wed, 16 Apr 2025 13:21:26 -0700 [thread overview]
Message-ID: <20250416202126.GD25659@frogsfrogsfrogs> (raw)
In-Reply-To: <Z__5LOpee2-5rIaE@casper.infradead.org>
On Wed, Apr 16, 2025 at 07:38:36PM +0100, Matthew Wilcox wrote:
> On Wed, Apr 16, 2025 at 11:08:37AM -0700, Darrick J. Wong wrote:
> > Hi folks,
> >
> > I upgraded my arm64 kernel to 6.15-rc2, and I also see this splat in
> > generic/363. The fstets config is as follows:
> >
> > MKFS_OPTIONS="-m metadir=1,autofsck=1,uquota,gquota,pquota, -b size=65536,"
> > MOUNT_OPTIONS=""
> >
> > The VM is arm64 with 64k base pages. I've disabled LBS to work around
> > a fair number of other strange bugs. Does this ring a bell for anyone?
> >
> > --D
> >
> > list_add double add: new=ffffffff40538c88, prev=fffffc03febf8148, next=ffffffff40538c88.
>
> Not a bell, but it's weird. We're trying to add ffffffff40538c88 to
> the list, but next already has that value. So this is a double-free of
> the folio? Do you have VM_BUG_ON_FOLIO enabled with CONFIG_VM_DEBUG?
Nope, but I can go re-add it to my kconfig and see what happens.
--D
next prev parent reply other threads:[~2025-04-16 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 18:08 [6.15-rc2 regression] iomap: null pointer in a bio completion Darrick J. Wong
2025-04-16 18:38 ` Matthew Wilcox
2025-04-16 20:21 ` Darrick J. Wong [this message]
2025-04-17 16:59 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250416202126.GD25659@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox