Linux XFS filesystem development
 help / color / mirror / Atom feed
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 updated
Date: Tue, 30 Aug 2022 08:12:17 -0700	[thread overview]
Message-ID: <Yw4o0fBFRqrCHQsY@magnolia> (raw)
In-Reply-To: <20220830115220.5s2nlztp56fbf4xa@andromeda>

On Tue, Aug 30, 2022 at 01:52:20PM +0200, Carlos Maiolino wrote:
> Hi folks,
> 
> The for-next branch of the xfsprogs repository at:
> 
>         git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> 
> has just been updated.
> 
> This update contains the initial libxfs sync to Linux 6.0 and should be turned
> into -rc0 once it (hopefully) gets some testing (and no complains) for more people.

Wooo, welcome, new maintainer! :)

> Please, if any questions, let me know.

For the repair deadlock fix[1], do you want me to pin the primary
superblock buffer to the xfs_mount like Dave suggested in [2]?

[1] https://lore.kernel.org/linux-xfs/166007921743.3294543.7334567013352169774.stgit@magnolia/
[2] https://lore.kernel.org/linux-xfs/20220811221541.GQ3600936@dread.disaster.area/

--D

> 
> The new head of the for-next branch is commit:
> 
> d3e53ab7c xfs: fix inode reservation space for removing transaction
> 
> 
> New Commits:
> 
> Andrey Strachuk (1):
>       [798d43495] xfs: removed useless condition in function xfs_attr_node_get
> 
> Dan Carpenter (1):
>       [17df7eb7e] xfs: delete unnecessary NULL checks
> 
> Darrick J. Wong (6):
>       [722e81c12] xfs: convert XFS_IFORK_PTR to a static inline helper
>       [7ff5f1edf] xfs: make inode attribute forks a permanent part of struct xfs_inode
>       [d4292c669] xfs: use XFS_IFORK_Q to determine the presence of an xattr fork
>       [4f8415858] xfs: replace XFS_IFORK_Q with a proper predicate function
>       [eae3e30d4] xfs: replace inode fork size macros with functions
>       [e373f06a3] xfs: don't leak memory when attr fork loading fails
> 
> Dave Chinner (17):
>       [ef78f876e] xfs: make last AG grow/shrink perag centric
>       [37dc5890e] xfs: kill xfs_ialloc_pagi_init()
>       [4330a9e00] xfs: pass perag to xfs_ialloc_read_agi()
>       [87db57baf] xfs: kill xfs_alloc_pagf_init()
>       [f9084bd95] xfs: pass perag to xfs_alloc_read_agf()
>       [bc87af992] xfs: pass perag to xfs_read_agi
>       [c1030eda4] xfs: pass perag to xfs_read_agf
>       [1d202c10b] xfs: pass perag to xfs_alloc_get_freelist
>       [9a73333d9] xfs: pass perag to xfs_alloc_put_freelist
>       [75c01cccf] xfs: pass perag to xfs_alloc_read_agfl
>       [83af0d13a] xfs: Pre-calculate per-AG agbno geometry
>       [8aa34dc9b] xfs: Pre-calculate per-AG agino geometry
>       [cee2d89ae] xfs: replace xfs_ag_block_count() with perag accesses
>       [54f6b9e5e] xfs: make is_log_ag() a first class helper
>       [0b2f4162b] xfs: rework xfs_buf_incore() API
>       [69535dadf] xfs: track the iunlink list pointer in the xfs_inode
>       [b9846dc9e] xfs: double link the unlinked inode list
> 
> Slark Xiao (1):
>       [e4a32219d] xfs: Fix typo 'the the' in comment
> 
> Xiaole He (1):
>       [ec36ecd2d] xfs: fix comment for start time value of inode with bigtime enabled
> 
> hexiaole (1):
>       [d3e53ab7c] xfs: fix inode reservation space for removing transaction
> 
> -- 
> Carlos Maiolino



  reply	other threads:[~2022-08-30 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 11:52 [ANNOUNCE] xfsprogs for-next updated Carlos Maiolino
2022-08-30 15:12 ` Darrick J. Wong [this message]
2022-08-31  9:43   ` Carlos Maiolino
2022-08-31 15:08     ` Darrick J. Wong
2022-09-01 10:55       ` Carlos Maiolino
  -- strict thread matches above, loose matches on Subject: below --
2022-11-16  9:58 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=Yw4o0fBFRqrCHQsY@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