All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: chandanbabu@kernel.org, djwong@kernel.org
Cc: david@fromorbit.com, dchinner@redhat.com, linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: fix reloading the last iunlink item
Date: Mon, 25 Sep 2023 08:39:04 -0700	[thread overview]
Message-ID: <169565625185.1980111.13370011821352297018.stg-ugh@frogsfrogsfrogs> (raw)

Hi Chandan,

Please pull this branch with changes for xfs for 6.6-rc3.

As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts.  Please let me know if you
encounter any problems.

--D

The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:

Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git tags/fix-fix-iunlink-6.6_2023-09-25

for you to fetch changes up to 537c013b140d373d1ffe6290b841dc00e67effaa:

xfs: fix reloading entire unlinked bucket lists (2023-09-24 18:12:13 -0700)

----------------------------------------------------------------
xfs: fix reloading the last iunlink item
It's not a good idea to be trying to send bug fixes to the mailing list
while also trying to take a vacation.  Dave sent some review comments
about the iunlink reloading patches, I changed them in djwong-dev, and
forgot to backport those changes to my -fixes tree.

As a result, the patch is missing some important pieces.  Perhaps
manually copying code diffs between email and two separate git trees
is archaic and stupid^W^W^W^Wisn't really a good idea?

This has been lightly tested with fstests.  Enjoy!

Signed-off-by: Darrick J. Wong <djwong@kernel.org>

----------------------------------------------------------------
Darrick J. Wong (1):
xfs: fix reloading entire unlinked bucket lists

fs/xfs/xfs_export.c | 16 ++++++++++++----
fs/xfs/xfs_inode.c  | 48 +++++++++++++++++++++++++++++++++++-------------
fs/xfs/xfs_itable.c |  2 ++
fs/xfs/xfs_qm.c     | 15 ++++++++++++---
4 files changed, 61 insertions(+), 20 deletions(-)

                 reply	other threads:[~2023-09-25 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=169565625185.1980111.13370011821352297018.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandanbabu@kernel.org \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    /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.