All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: cem@kernel.org, djwong@kernel.org
Cc: bodonnel@redhat.com, hch@lst.de, linux-xfs@vger.kernel.org
Subject: [GIT PULL 06/11] xfsprogs: bug fixes for 6.8
Date: Wed, 17 Apr 2024 15:08:53 -0700	[thread overview]
Message-ID: <171339160291.1911630.16552547686432095856.stg-ugh@frogsfrogsfrogs> (raw)
In-Reply-To: <20240417220440.GB11948@frogsfrogsfrogs>

Hi Carlos,

Please pull this branch with changes for xfsprogs for 6.6-rc1.

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.

The following changes since commit 2f2e6b36a22c510964fa920b15726526aa102e2c:

xfs_repair: bulk load records into new btree blocks (2024-04-17 14:06:27 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git tags/xfsprogs-fixes-6.8_2024-04-17

for you to fetch changes up to 16a75c71b4c04373c0c726b8e6ddfd030a81c93e:

xfs_io: add linux madvise advice codes (2024-04-17 14:06:27 -0700)

----------------------------------------------------------------
xfsprogs: bug fixes for 6.8 [06/20]

Bug fixes for xfsprogs for 6.8.

This has been running on the djcloud for months with no problems.  Enjoy!

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

----------------------------------------------------------------
Darrick J. Wong (5):
xfs_repair: double-check with shortform attr verifiers
xfs_db: improve number extraction in getbitval
xfs_scrub: fix threadcount estimates for phase 6
xfs_scrub: don't fail while reporting media scan errors
xfs_io: add linux madvise advice codes

db/bit.c             | 37 +++++++++++--------------
io/madvise.c         | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++-
repair/attr_repair.c | 17 ++++++++++++
scrub/phase6.c       | 36 ++++++++++++++++++------
4 files changed, 137 insertions(+), 30 deletions(-)


  parent reply	other threads:[~2024-04-17 22:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 22:04 [GIT PULLBOMB] xfsprogs: catch us up to 6.8, at least Darrick J. Wong
2024-04-17 22:07 ` [GIT PULL 01/11] xfsprogs: packaging fixes for 6.7 Darrick J. Wong
2024-04-18  4:31   ` Christoph Hellwig
2024-04-22  9:56   ` Carlos Maiolino
2024-04-17 22:07 ` [GIT PULL 02/11] xfsprogs: minor " Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 03/11] xfsprogs: convert utilities to use new rt helpers Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 04/11] libxfs: sync with 6.8 Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 05/11] xfs_repair: faster btree bulkloading Darrick J. Wong
2024-04-17 22:08 ` Darrick J. Wong [this message]
2024-04-17 22:09 ` [GIT PULL 07/11] xfsprogs: fix log sector size detection Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 08/11] mkfs: scale shards on ssds Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 09/11] xfs_scrub: scan metadata files in parallel Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 10/11] xfs_repair: rebuild inode fork mappings Darrick J. Wong
2024-04-17 22:10 ` [GIT PULL 11/11] xfs_repair: support more than 4 billion records Darrick J. Wong

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=171339160291.1911630.16552547686432095856.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bodonnel@redhat.com \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --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.