public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
	zlang@kernel.org, djwong@kernel.org, fstests@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: test log recovery for extent frees right after growfs
Date: Tue, 10 Sep 2024 13:34:20 +0200	[thread overview]
Message-ID: <20240910113420.GA7326@lst.de> (raw)
In-Reply-To: <20240910085748.jcea37l665dxluge@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Tue, Sep 10, 2024 at 04:57:48PM +0800, Zorro Lang wrote:
> On Tue, Sep 10, 2024 at 07:31:17AM +0300, Christoph Hellwig wrote:
> > Reproduce a bug where log recovery fails when an unfinised extent free
> > intent is in the same log as the growfs transaction that added the AG.
> 
> Which bug? If it's a regression test, can we have a _fixed_by_kernel_commit
> to mark the known issue?

I just sent the kernel patches for it.  It's been there basically
forever as far as I can tell.


  reply	other threads:[~2024-09-10 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  4:31 [PATCH] xfs: test log recovery for extent frees right after growfs Christoph Hellwig
2024-09-10  8:57 ` Zorro Lang
2024-09-10 11:34   ` Christoph Hellwig [this message]
2024-09-10 14:19 ` Brian Foster
2024-09-10 15:10   ` Christoph Hellwig
2024-09-10 16:13     ` Brian Foster
2024-10-08 16:28       ` Brian Foster
2024-10-09  8:04         ` Christoph Hellwig
2024-10-09 12:35           ` Brian Foster
2024-10-09 12:43             ` Christoph Hellwig
2024-10-09 15:14               ` Brian Foster
2024-10-10  6:51                 ` Christoph Hellwig
2024-10-14  6:00                 ` Christoph Hellwig

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=20240910113420.GA7326@lst.de \
    --to=hch@lst.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@kernel.org \
    --cc=zlang@redhat.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