From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs for-next updated
Date: Wed, 31 Aug 2022 11:43:25 +0200 [thread overview]
Message-ID: <20220831094325.5dwjygbcd5mcibok@andromeda> (raw)
In-Reply-To: <Yw4o0fBFRqrCHQsY@magnolia>
On Tue, Aug 30, 2022 at 08:12:17AM -0700, Darrick J. Wong wrote:
> 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! :)
\o/
>
> > 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]?
I'd rather have it pinned to the xfs_mount as it's often accessed, do you think
it is doable (you mentioned you've ran into many problems with that)?
I didn't have time to try to reproduce those deadlocks yet though.
>
> [1] https://lore.kernel.org/linux-xfs/166007921743.3294543.7334567013352169774.stgit@magnolia/
> [2] https://lore.kernel.org/linux-xfs/20220811221541.GQ3600936@dread.disaster.area/
--
Carlos Maiolino
next prev parent reply other threads:[~2022-08-31 9:43 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
2022-08-31 9:43 ` Carlos Maiolino [this message]
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=20220831094325.5dwjygbcd5mcibok@andromeda \
--to=cem@kernel.org \
--cc=djwong@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