From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs for-next branch updated
Date: Mon, 21 Nov 2022 16:25:25 -0800 [thread overview]
Message-ID: <Y3wW9SCRYmBX3K9a@magnolia> (raw)
In-Reply-To: <20221121143547.m33n36fufbz2x626@andromeda>
On Mon, Nov 21, 2022 at 03:35:47PM +0100, Carlos Maiolino wrote:
> Hello.
>
> The xfsprogs, for-next branch located at:
>
> https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=for-next
>
> has just been updated.
>
> The new head is:
>
> b827e2318 xfs: fix sb write verify for lazysbcount
>
>
> This update contains only the libxfs-sync for Linux 6.1, and will serve as a
> base for the xfsprogs 6.1 release.
> Please, let me know if any issue.
>
>
> The following commits are now in the for-next tree:
>
> [b827e2318] xfs: fix sb write verify for lazysbcount
Why was this commit merged for xfsprogs 6.1? That patch is queued for
kernel 6.2 in for-next, but the merge window is not open yet.
--D
> [7257eb3ed] xfs: rename XFS_REFC_COW_START to _COWFLAG
> [7accbcd00] xfs: fix uninitialized list head in struct xfs_refcount_recovery
> [8b2b27581] xfs: fix agblocks check in the cow leftover recovery function
> [817ea9f0f] xfs: check record domain when accessing refcount records
> [f275d70e8] xfs: remove XFS_FIND_RCEXT_SHARED and _COW
> [cc2a3c2ad] xfs: refactor domain and refcount checking
> [8160aeff0] xfs: report refcount domain in tracepoints
> [6b2f464dd] xfs: track cow/shared record domains explicitly in xfs_refcount_irec
> [bec88ec72] xfs: move _irec structs to xfs_types.h
> [7ccbdec2b] xfs: check deferred refcount op continuation parameters
> [b3f9ae08e] xfs: create a predicate to verify per-AG extents
> [2d5166b9d] xfs: make sure aglen never goes negative in xfs_refcount_adjust_extents
> [4b69afdc4] xfs: refactor all the EFI/EFD log item sizeof logic
> [d267ac6a0] xfs: fix memcpy fortify errors in EFI log format copying
> [227bc97f1] xfs: increase rename inode reservation
> [20798cc06] xfs: fix exception caused by unexpected illegal bestcount in leaf dir
> [11d2f5afc] treewide: use get_random_u32() when possible
> [4947ac5b3] treewide: use prandom_u32_max() when possible, part 1
> [1a3bfffee] xfs: rearrange the logic and remove the broken comment for xfs_dir2_isxx
> [04d4c27af] xfs: trim the mapp array accordingly in xfs_da_grow_inode_int
> [e8dbbca18] xfs: Remove the unneeded result variable
> [be98db856] xfs: clean up "%Ld/%Lu" which doesn't meet C standard
>
>
> --
> Carlos Maiolino
next prev parent reply other threads:[~2022-11-22 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 14:35 [ANNOUNCE] xfsprogs for-next branch updated Carlos Maiolino
2022-11-22 0:25 ` Darrick J. Wong [this message]
2022-11-22 9:53 ` Carlos Maiolino
2022-11-22 19:48 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 13:01 Carlos Maiolino
2022-12-16 11:16 Carlos Maiolino
2022-12-22 7:44 Carlos Maiolino
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=Y3wW9SCRYmBX3K9a@magnolia \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox