All of lore.kernel.org
 help / color / mirror / Atom feed
From: yebin <yebin@huaweicloud.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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 15:19:43 +0800	[thread overview]
Message-ID: <693FB68F.50400@huaweicloud.com> (raw)
In-Reply-To: <aT-eo76enT15FKkr@infradead.org>



On 2025/12/15 13:37, Christoph Hellwig wrote:
> Can you add a sentence or two here how you found the issue?
>

First, we encountered the issue described in 
https://access.redhat.com/solutions/6095011 in our production 
environment.The triggered scenario is that after performing fragmented 
organization, the system suddenly lost power and reset, and then 
encountered a panic when mounting the XFS file system.
After analyzing the vmcore, we identified the cause of the issue. 
Subsequently, while reproducing the issue on linux-next, we also 
discovered the problem described in PATCH[1].

> 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.
>


  reply	other threads:[~2025-12-15  7:19 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 [this message]
2025-12-15 14:29     ` Christoph Hellwig
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=693FB68F.50400@huaweicloud.com \
    --to=yebin@huaweicloud.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=yebin10@huawei.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.