From: Christoph Hellwig <hch@infradead.org>
To: yebin <yebin@huaweicloud.com>
Cc: Christoph Hellwig <hch@infradead.org>,
djwong@kernel.org, linux-xfs@vger.kernel.org,
chandan.babu@oracle.com, dchinner@redhat.com, yebin10@huawei.com
Subject: Re: [PATCH 0/2] Fix two issues about swapext
Date: Mon, 15 Dec 2025 06:29:48 -0800 [thread overview]
Message-ID: <aUAbXIkQ_LfYuPJc@infradead.org> (raw)
In-Reply-To: <693FB68F.50400@huaweicloud.com>
On Mon, Dec 15, 2025 at 03:19:43PM +0800, yebin wrote:
> First, we encountered the issue described in
> https://access.redhat.com/solutions/6095011 in our production
That's behind a paywall unfortunately.
> > Any chance you could add a reproducer to xfstests?
> >
> Yes, this issue is quite reproducible. It occurs inevitably when following
> certain steps. This problem has existed for a long time. I think the reason
> it's not easily detected is that the XFS_IOC_SWAPEXT IOCTL command is
> generally used during defragmentation. Therefore, it is almost never
> included in typical log replay scenarios.
Can you send out an xfstests for this? Or at least a shell script
fragment?
next prev parent reply other threads:[~2025-12-15 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 3:59 [PATCH 0/2] Fix two issues about swapext Ye Bin
2025-12-13 3:59 ` [PATCH 1/2] xfs: fix checksum error when call xfs_recover_inode_owner_change() Ye Bin
2025-12-13 3:59 ` [PATCH 2/2] xfs: fix xfs_recover_inode_owner_change() failed Ye Bin
2025-12-15 5:37 ` [PATCH 0/2] Fix two issues about swapext Christoph Hellwig
2025-12-15 7:19 ` yebin
2025-12-15 14:29 ` Christoph Hellwig [this message]
2025-12-16 9:31 ` yebin
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=aUAbXIkQ_LfYuPJc@infradead.org \
--to=hch@infradead.org \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yebin10@huawei.com \
--cc=yebin@huaweicloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.