All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Weiming Shi <bestswngs@gmail.com>
Cc: linux-xfs@vger.kernel.org, Carlos Maiolino <cem@kernel.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Brian Foster <bfoster@redhat.com>, Xiang Mei <xmei5@asu.edu>
Subject: Re: [PATCH] xfs: fail recovery on a committed log item with no regions
Date: Wed, 1 Jul 2026 04:14:48 -0700	[thread overview]
Message-ID: <akT2qDLIwGHHkWIB@infradead.org> (raw)
In-Reply-To: <akTzkmAwaDkAK_mM@infradead.org>

On Wed, Jul 01, 2026 at 04:01:38AM -0700, Christoph Hellwig wrote:
> So maybe as a prep-patch remove the existing ASSERT(0), then as
> a second prep patch move the list splicing after the loop:
> 
> 	if (error) {
> 		/*
> 		 * Return the remaining items back to the transaction item list
> 		 * so they can be freed in caller.
>                  */
> 		if (!list_empty(&sort_list))
> 			list_splice_init(&sort_list, &trans->r_itemq);
> 	} else {
> 		ASSERT(list_empty(&sort_list));
> 	}

Actually just always doing the split back might be even better:

	/*
	 * Return the remaining items back to the transaction item list so they
	 * can be freed in caller.  This should only happen when we encountered
	 * an error.
	 */
	if (!list_empty(&sort_list)) {
		ASSERT(error);
		list_splice_init(&sort_list, &trans->r_itemq);
	}

  reply	other threads:[~2026-07-01 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 16:24 [PATCH] xfs: fail recovery on a committed log item with no regions Weiming Shi
2026-07-01 11:01 ` Christoph Hellwig
2026-07-01 11:14   ` Christoph Hellwig [this message]
2026-07-01 15:43     ` Weiming Shi

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=akT2qDLIwGHHkWIB@infradead.org \
    --to=hch@infradead.org \
    --cc=bestswngs@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xmei5@asu.edu \
    /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.