Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: linux-xfs@vger.kernel.org, alexjlzheng@tencent.com,
	bfoster@redhat.com, cem@kernel.org, cmaiolino@redhat.com,
	dgc@kernel.org, hch@lst.de, liuhuan01@kylinos.cn,
	msinguru@redhat.com, romain.naour@smile.fr,
	syzbot+0391d34e801643e2809b@syzkaller.appspotmail.com,
	wilfred.mallawa@wdc.com, ytohnuki@amazon.com
Subject: Re: [ANNOUNCE] xfsprogs: v7.1.0 released
Date: Mon, 13 Jul 2026 08:54:05 -0700	[thread overview]
Message-ID: <20260713155405.GC7195@frogsfrogsfrogs> (raw)
In-Reply-To: <alDUTZkDnQodyG2R@aalbersh-thinkpadx1carbongen13.rmtcz.csb>

On Mon, Jul 13, 2026 at 11:23:41AM +0200, Andrey Albershteyn wrote:
> Hi folks,
> 
> The xfsprogs master branch in repository at:
> 
> 	git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> 
> has just been updated.
> 
> This release consist mostly of a bunch of fixes for xfs_scrub and xfs_healer
> found with help of Codex. The xfs_scrub systemd units now have less security
> restrictions due to issues with postfix. Multiple memory leaks and overflows
> fixed. A lot of fixes for xfs_scrub phased repair flow. xfs_protofile now also
> works with non-directories. The build system is fixed for path containing ".o".
> Manual pages and mkfs messages now have correct MiB units.
> 
> Patches often get missed, so if your outstanding patches are properly reviewed
> on the list and not included in this update, please let me know.
> 
> The for-next branch has also been updated to match the state of master.
> 
> The new head of the master branch is commit:
> 
> e80b048d87fdc5735e0d03ae29b497b402ea8bbe
> 
> New commits:
> 
> Andrey Albershteyn (1):
>       [e80b048d87fd] xfsprogs: Release v7.1.0
> 
> Christoph Hellwig (1):
>       [846570fc6498] xfs: switch (back) to a per-buftarg buffer hash
> 
> Darrick J. Wong (65):
>       [1aadfecf6afb] xfs_healer: fix error reporting
>       [d21aab594247] xfs_healer: recommend offline fsck for XCORRUPT repairs
>       [44849c72c720] xfs_healer: initialize variable here
>       [fc76bac6ce1f] xfs_healer: run a full xfs_scrub repair if we don't know how to do a spot repair
>       [79551362141a] xfs_healer: fix Makefile errors
>       [4d62c2fa83ba] xfs_healer: don't leak wh->mntpoint if fd_to_handle fails
>       [a6b85058f1ae] xfs_healer: coordinate access to weakhandle::mntpoint correctly
>       [de2bc2763b53] xfs_scrub_media_fail: reduce security lockdowns to avoid postfix problems
>       [ff0aeb233200] xfs_scrub_all: fix broken command line string array construction
>       [ee3ea981af6b] xfs_scrub_all_fail: reduce security lockdowns to avoid postfix problems
>       [24362b13fb76] xfs_scrub_fail: send content headers for xfs_scrub_all failures
>       [472b010d0c84] xfs_scrub: fix uninitialized variable
>       [a42fc3ec97db] xfs_scrub: fix integer overflows
>       [9d36b3db1212] xfs_scrub: don't count internal log space in the data device used count
>       [064834b6a0a2] xfs_scrub: widen scrub and repair dependency mask
>       [44eee006149b] xfs_scrub: fix work estimation for rtgroups filesystems
>       [5db0a8b13358] xfs_scrub: don't report media errors in specially-owned areas as file data
>       [b65854f9e580] xfs_scrub: return SCRUB_RET_OPERROR if unicode collision detection fails to initialize
>       [a34231de7668] xfs_scrub: fix nonsense advice after a scrub finds errors
>       [25c97ededd3e] xfs_scrub: don't allow NAN as fstrim percentage
>       [709b7eab8977] xfs_scrub: reset bulkstat pointer on retry
>       [dc4e11fa3d7c] xfs_scrub: don't return garbage value from bulkstat_the_rest
>       [d0b07b57faf0] xfs_scrub: don't continue with phase1 if autofsck=none
>       [4a093a994c63] xfs_scrub: don't crash trying to complain about clean health
>       [353333f0f3ff] xfs_scrub: fix inverted return value from ptvar_get
>       [a5732e6c61f5] xfs_scrub: don't obscure repair failures in repair_list_schedule
>       [33cc9bbc4dce] xfs_scrub: bitmap iteration functions must retur
>       [5556c32a0304] xfs_scrub: read verification isn't ok if it hit runtime errors
>       [359eeef71fae] libfrog: fix buffer overflow in getparents path_to_string
>       [5b0f430d8e59] xfs_healer: don't allow aliasing of mon_fd in setup_monitor
>       [425126caa89c] xfs_healer_start: check listmount when doing a --check
>       [577d6415adbb] xfs_healer_start: fix static checking
>       [76ef8d90a3f0] xfs_healer_start: increase statmount buffer size
>       [a0f50dec3540] xfs_healer: allow AF_UNIX socket access for xfs_healer instances
>       [f6505519ef79] xfs_healer: don't put the slice file in LDIRT
>       [64344c43430a] xfs_scrub: handle missing media verify ioctl failure return codes
>       [2712427c08a5] xfs_scrub: report bad file ranges correctly
>       [3e4bb144f657] xfs_scrub: handle media scans of internal rt devices correctly
>       [c001fa7d4db4] xfs_scrub: track inode scan abort state with an enum
>       [bc9371417a61] xfs_scrub: don't skip bulkstat batch when scrub_scan_user_files helper returns ESTALE
>       [b6dba3d85ae5] xfs_scrub: warn about incomplete repairs if we never get to them
>       [e2df9f9bb984] xfs_scrub: report external log space usage in phase 7
>       [243048f90dd4] xfs_scrub: account only data extent tail after an overlap
>       [baef30aabbd5] xfs_scrub: account for reflinked realtime file data
>       [a4080cef33fd] xfs_scrub: don't leak the autofsck fsproperty handle
>       [157d76940c3c] xfs_scrub: warn about difficult rtgroup repairs
>       [0bafb12d66e7] xfs_scrub: stop user file scan if caller already aborted
>       [bac5085ac2e3] xfs_scrub: don't flatten error numbers in read_verify_schedule_now
>       [b43e9064d665] xfs_scrub: actually handle NEEDSCHECK scrub items in phase 4
>       [41530a0981a1] xfs_scrub: don't leak phase 5 scan items after a failed workqueue_add
>       [f4dfa0b0c565] xfs_scrub: fix phase 8 debug reporting
>       [f75bb3f2d598] xfs_scrub: always finish cleanup, even if reporting healthy state fails
>       [4399db49dec0] xfs_scrub: fix spacemap external log device scan dev key
>       [70d0a4f27464] xfs_scrub: fix estimate of work items for phase 4
>       [b64c29f5bfed] xfs_db: fix type conversions
>       [1bbedb6d165e] xfs_db: dump zoned filesystem superblock fields
>       [7a26df144fad] xfs_healer: fix getmntent race in weakhandle
>       [b07c386bc60b] mkfs: don't redefine DIRT for protofiles
>       [2df5f48fb829] mkfs: fix PATH_MAX check
>       [46b0ee102f25] mkfs: fix symlink target length check in create_nondir_inode
>       [b3268fb3d822] xfs_protofile: make nondirectory arguments actually work
>       [a2b765f7d0fd] mkfs: pass stat buf pointers around the protofile code
>       [63a4a9d6966c] mkfs: fix hardlink detection in directory import code
>       [8c6bf6721ac4] mkfs: PQUOTA shouldn't conflict with GQNOENFORCE
>       [074c18165ea3] xfs_scrub: fix spacemap scan for internal rt devices

Hmmm, this patch seems to have gotten the same rtstart hunk pasted into
both scan_ag_rmaps and scan_rtg_rmaps even though the original patch
only changed scan_rtg_rmaps.  I'll send a fix.

--D

> Jinliang Zheng (1):
>       [bae44fee8d42] xfs: remove the meaningless XFS_ALLOC_FLAG_FREEING
> 
> Manognya Singuru (1):
>       [ec7424231d53] mkfs: fix filesystem and log size units
> 
> Romain Naour (1):
>       [188dc92e4e57] xfsprogs: include/buildrules: fix ltdep
> 
> Wilfred Mallawa (1):
>       [270a5f354ab7] xfs: add write pointer to xfs_rtgroup_geometry
> 
> Yuto Ohnuki (2):
>       [c957be18e5e5] xfs: zero entire directory data block header region at init
>       [622d715e372d] xfs: zero directory data block padding on write verification
> 
> liuh (2):
>       [708b369bdf8f] mkfs: remove duplicate include of convert.h
>       [d89fea99c26e] fsr: preserve xfrog_bulkstat error codes
> 
> Code Diffstat:
> 
>  VERSION                                |  4 +-
>  configure.ac                           |  2 +-
>  db/io.c                                |  9 +++-
>  db/sb.c                                | 10 ++++
>  debian/changelog                       |  6 +++
>  doc/CHANGES                            | 52 ++++++++++++++++++++
>  fsr/xfs_fsr.c                          |  2 +-
>  healer/Makefile                        |  9 +++-
>  healer/fsrepair.c                      | 28 +++++++++--
>  healer/weakhandle.c                    | 76 ++++++++++++++++++++++-------
>  healer/xfs_healer.c                    | 10 ++--
>  healer/xfs_healer@.service.in          |  4 +-
>  healer/xfs_healer_start.c              | 43 ++++++++++++++--
>  include/buildrules                     |  2 +-
>  libfrog/getparents.c                   |  2 +-
>  libxfs/xfs_ag.c                        | 13 +----
>  libxfs/xfs_ag.h                        |  2 -
>  libxfs/xfs_dir2_data.c                 | 18 ++++---
>  libxfs/xfs_fs.h                        |  5 +-
>  libxfs/xfs_refcount.c                  |  3 +-
>  man/man8/mkfs.xfs.8.in                 |  6 +--
>  mkfs/Makefile                          |  2 +-
>  mkfs/proto.c                           | 55 ++++++++++++---------
>  mkfs/xfs_mkfs.c                        | 17 +++----
>  mkfs/xfs_protofile.py.in               | 40 +++++++++------
>  scrub/inodes.c                         | 89 +++++++++++++++++++++++-----------
>  scrub/phase1.c                         | 26 ++++++----
>  scrub/phase2.c                         | 10 +++-
>  scrub/phase3.c                         |  4 +-
>  scrub/phase4.c                         | 28 ++++++++---
>  scrub/phase5.c                         | 12 +++--
>  scrub/phase6.c                         | 56 +++++----------------
>  scrub/phase7.c                         | 86 +++++++++++++++++++-------------
>  scrub/phase8.c                         |  7 ++-
>  scrub/read_verify.c                    | 12 +++--
>  scrub/repair.c                         | 31 +++++++-----
>  scrub/repair.h                         | 14 ++++++
>  scrub/scrub.c                          | 23 ++++++---
>  scrub/scrub_private.h                  |  2 +-
>  scrub/spacemap.c                       | 45 ++++++++++++-----
>  scrub/spacemap.h                       | 42 ++++++++++++++++
>  scrub/xfs_scrub.c                      | 18 +++++--
>  scrub/xfs_scrub.h                      |  2 +-
>  scrub/xfs_scrub_all.py.in              |  2 +-
>  scrub/xfs_scrub_all_fail.service.in    | 59 +++-------------------
>  scrub/xfs_scrub_fail.in                |  2 +
>  scrub/xfs_scrub_media_fail@.service.in | 58 ++--------------------
>  47 files changed, 652 insertions(+), 396 deletions(-)
> 
> -- 
> - Andrey
> 

  reply	other threads:[~2026-07-13 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  9:23 [ANNOUNCE] xfsprogs: v7.1.0 released Andrey Albershteyn
2026-07-13 15:54 ` Darrick J. Wong [this message]
2026-07-13 18:02   ` Andrey Albershteyn
2026-07-13 18:15     ` Darrick J. Wong
2026-07-13 18:36       ` Andrey Albershteyn

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=20260713155405.GC7195@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=alexjlzheng@tencent.com \
    --cc=bfoster@redhat.com \
    --cc=cem@kernel.org \
    --cc=cmaiolino@redhat.com \
    --cc=dgc@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=liuhuan01@kylinos.cn \
    --cc=msinguru@redhat.com \
    --cc=romain.naour@smile.fr \
    --cc=syzbot+0391d34e801643e2809b@syzkaller.appspotmail.com \
    --cc=wilfred.mallawa@wdc.com \
    --cc=ytohnuki@amazon.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