From: Dave Chinner <dgc@kernel.org>
To: Guikun Yang <yangguikun19@qq.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: xfs: XLOG_WAS_CONT_TRANS on a transaction with no buffered regions reads ri_buf[-1] - null deref Oops during mount log recovery
Date: Tue, 10 Nov 2026 08:22:31 +1100 [thread overview]
Message-ID: <avI5l1074Qgn-ypN@dread> (raw)
In-Reply-To: <tencent_11C734248ADE0736CA2735F63B7064C76905@qq.com>
On Sat, Nov 07, 2026 at 10:00:00AM +0800, Guikun Yang wrote:
> Hi,
>
> Mounting an XFS volume whose log record after the transaction header
> carries an operation header with the XLOG_WAS_CONT_TRANS flag panics
> the kernel during log recovery - on a stock kernel, no sanitizer
> configuration needed:
>
> BUG: unable to handle page fault for address: fffffffffffffff0
> #PF: supervisor read access in kernel mode
> Oops: Oops: 0000 [#1] SMP KASAN PTI
> RIP: xlog_recover_add_to_cont_trans+0xf9/0x460
> xlog_recovery_process_trans
> xlog_recover_process_ophdr
> xlog_recover_process_data
> xlog_recover_process
> xlog_do_recovery_pass
> Kernel panic - not syncing: Fatal exception
Please stop with all these bug reports about things we -already know
are not validated- and -are already being fixed-.
https://lore.kernel.org/linux-xfs/20261013060204.3138690-1-dgc@kernel.org/
Please run all your tests and analysis on the log verification
series that addresses all these problems, and find holes in that
series that still need to be plugged.
Do *not waste our time* reporting known problems that we are
actively fixing. Make yourself and your LLM tokens useful by
creating fstests reporducers for all the issues and then -testing
the proposed fixes- and giving feedback on the fixes that already
exist.
-Dave.
--
Dave Chinner
dgc@kernel.org
next prev parent reply other threads:[~2026-11-09 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 2:00 Guikun Yang
2026-11-09 21:22 ` Dave Chinner [this message]
[not found] <c30-xfs-wascont-rideref-20261107@qq.com>
2026-11-07 12:00 ` Guikun Yang
[not found] ` <c31-xfs-logged-sb-geometry-20261107@qq.com>
2026-11-08 4:00 ` Guikun Yang
[not found] ` <c34-xfs-ilf-len-oob-20261108@qq.com>
2026-11-09 2:00 ` Guikun Yang
[not found] ` <c37-xfs-ilf-size-short-region-20261109@qq.com>
2026-11-09 8:00 ` Guikun Yang
[not found] ` <c40-xfs-inodebuf-item-index-20261109@qq.com>
2026-11-09 12:00 ` Guikun Yang
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=avI5l1074Qgn-ypN@dread \
--to=dgc@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yangguikun19@qq.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®