From: Christoph Hellwig <hch@lst.de>
To: "Lai, Yi" <yi1.lai@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH 1/3] xfs: also flush the RT device cache in xlog_write_iclog
Date: Fri, 18 Sep 2026 13:24:50 +0200 [thread overview]
Message-ID: <20260918112450.GA15716@lst.de> (raw)
In-Reply-To: <aquGEi4DdTPqdQEh@ly-workstation>
On Thu, Sep 17, 2026 at 02:17:54PM +0800, Lai, Yi wrote:
>
> I used Syzkaller and found that there is INFO: task hung in xfs_buf_item_unpin in v7.3-rc3 kernel.
Looks like it is temporary and then your test continues after this?
Could it be that the RT device is backed by something very slow
and you're just seeing that delay?
>
> After bisection and the first bad commit is:
> "
> ad0033e2dbd3 xfs: also flush the RT device cache in xlog_write_iclog
> "
>
> All detailed into can be found at:
> https://github.com/laifryiee/syzkaller_logs/tree/main/260916_125217_xfs_buf_item_unpin
> Syzkaller repro code:
> https://github.com/laifryiee/syzkaller_logs/tree/main/260916_125217_xfs_buf_item_unpin/repro.c
That looks like mostly binary code, really hard to make any sense of
that.
next prev parent reply other threads:[~2026-09-18 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 7:33 fix cache flushes for the RT device Christoph Hellwig
2026-09-07 7:33 ` [PATCH 1/3] xfs: also flush the RT device cache in xlog_write_iclog Christoph Hellwig
2026-09-10 10:40 ` Carlos Maiolino
2026-09-17 6:17 ` Lai, Yi
2026-09-18 11:24 ` Christoph Hellwig [this message]
2026-09-07 7:33 ` [PATCH 2/3] xfs: don't continue on error in xfs_fsync Christoph Hellwig
2026-09-10 10:40 ` Carlos Maiolino
2026-09-07 7:33 ` [PATCH 3/3] xfs: avoid extra cache flushes for multi-device file systems " Christoph Hellwig
2026-09-10 10:43 ` Carlos Maiolino
2026-09-11 7:29 ` fix cache flushes for the RT device Carlos Maiolino
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=20260918112450.GA15716@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yi1.lai@intel.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