From: Carlos Maiolino <cem@kernel.org>
To: Aditya Prakash Srivastava <aditya.ansh182@gmail.com>
Cc: "Darrick J . Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/1] xfs: prevent close() hangs on frozen filesystems
Date: Wed, 16 Sep 2026 14:06:48 +0200 [thread overview]
Message-ID: <178956040899.10466.11807387586827569205.b4-ty@kernel.org> (raw)
In-Reply-To: <20260914093152.1698-1-aditya.ansh182@gmail.com>
On Mon, 14 Sep 2026 09:31:50 +0000, Aditya Prakash Srivastava wrote:
> This is version 6 of the patch series addressing the close() system
> call hanging indefinitely on frozen XFS filesystems (Bugzilla #205833).
>
> In v5, I introduced a transaction allocation flag
> (XFS_TRANS_WRITECOUNT_TRYLOCK) to handle the trylock inside
> __xfs_trans_alloc() and propagated it down to xfs_free_eofblocks().
> Christoph suggested this design and reviewed the implementation.
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: prevent close() from hanging on frozen filesystems
commit: 6fdfe8606f99d86bdd109c94ef0821b8529fe44b
Best regards,
--
Carlos Maiolino <cem@kernel.org>
next prev parent reply other threads:[~2026-09-16 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 9:31 Aditya Prakash Srivastava
2026-09-14 9:31 ` [PATCH v6 1/1] xfs: prevent close() from hanging " Aditya Prakash Srivastava
2026-09-14 14:59 ` Darrick J. Wong
2026-09-15 6:37 ` Christoph Hellwig
2026-09-16 12:06 ` Carlos Maiolino [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-14 8:28 [PATCH v6 0/1] xfs: prevent close() hangs " Aditya Prakash Srivastava
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=178956040899.10466.11807387586827569205.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=aditya.ansh182@gmail.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®