From: Christoph Hellwig <hch@infradead.org>
To: cen zhang <zzzccc427@gmail.com>
Cc: cem@kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, zhenghaoran154@gmail.com,
r33s3n6@gmail.com, gality365@gmail.com,
linux-xfs@vger.kernel.org
Subject: Re: [BUG] xfs: Assertion failure in dio_write( flags & IOMAP_DIO_OVERWRITE_ONLY) with a UAF
Date: Mon, 11 Aug 2025 03:45:46 -0700 [thread overview]
Message-ID: <aJnJ2jnFdu9V-j1Z@infradead.org> (raw)
In-Reply-To: <CAFRLqsXrTagA7woSffBUUPUQ12VK1Ks292FT=miCv_NQktJY1A@mail.gmail.com>
On Wed, Aug 06, 2025 at 07:40:19PM +0800, cen zhang wrote:
> Hello maintainers,
>
> I would like to report a kernel panic found using syzkaller on a 6.16.0-rc6.
>
> The kernel log shows two distinct but closely timed crash reports,
> which I guess are related.
>
> 1. An XFS assertion failure: Assertion failed: flags &
> IOMAP_DIO_OVERWRITE_ONLY, file: fs/xfs/xfs_file.c, line: 876 triggered
> by a write() system call in xfs_file_dio_write_unaligned.
>
> 2. A KASAN use-after-free report on a task_struct object, triggered
> during an ioctl() call (likely FICLONE or FIDEDUPERANGE). The crash
> occurs in rwsem_down_write_slowpath when trying to lock an inode via
> xfs_reflink_remap_prep.
>
> Unfortunately, I have not been able to create a standalone C
> reproducer, and attempts to use syzkaller's repro tool on the syz-prog
> have not reliably triggered the bug again.
Thanks for the report, but it will be really hard to do anything without
a reproducer. I case you are still trying to create one it would be
great to hear if you have one!
prev parent reply other threads:[~2025-08-11 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 11:40 cen zhang
2025-08-11 10:45 ` Christoph Hellwig [this message]
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=aJnJ2jnFdu9V-j1Z@infradead.org \
--to=hch@infradead.org \
--cc=baijiaju1990@gmail.com \
--cc=cem@kernel.org \
--cc=gality365@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=r33s3n6@gmail.com \
--cc=zhenghaoran154@gmail.com \
--cc=zzzccc427@gmail.com \
/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
all inboxes | Powered by JetHome®