From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Aditya Prakash Srivastava <aditya.ansh182@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] xfs: prevent close() from hanging on frozen filesystems
Date: Fri, 14 Aug 2026 18:25:41 +0200 [thread overview]
Message-ID: <an9BQdSqrmzYhB3l@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <an7Dk2Tn1ibCRsv2@infradead.org>
On Fri, Aug 14, 2026 at 12:28:19AM -0700, Christoph Hellwig wrote:
> On Thu, Aug 13, 2026 at 09:43:44PM +0530, Aditya Prakash Srivastava wrote:
> >
> > Are there any remaining concerns or feedback that need
> > to be addressed with this patch?
>
> Still looks good to me, but I think it just go lost. It's a bit close
> for the 7.3 merge window now, but I'd suggest you resend it in a week
> or two to get it onto the agenda for 7.4 early.
Yup, I was waiting for Darrick to follow-up then it fell on limbo.
Please follow Christoph's advice, please rebase and re-send on top of
the tree after 7.3 merge window.
next prev parent reply other threads:[~2026-08-14 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 5:38 [PATCH v5 0/2] xfs: resolve close() deadlocks on frozen filesystems Aditya Srivastava
2026-06-16 5:38 ` [PATCH v5 1/2] xfs: add a XFS_TRANS_WRITECOUNT_TRYLOCK flag Aditya Srivastava
2026-06-16 5:38 ` [PATCH v5 2/2] xfs: prevent close() from hanging on frozen filesystems Aditya Srivastava
2026-06-16 13:04 ` Christoph Hellwig
2026-06-24 17:35 ` Darrick J. Wong
2026-06-24 18:28 ` Aditya Prakash Srivastava
2026-07-08 13:19 ` Aditya Prakash Srivastava
2026-08-13 16:13 ` Aditya Prakash Srivastava
2026-08-14 7:28 ` Christoph Hellwig
2026-08-14 16:25 ` Carlos Maiolino [this message]
2026-08-14 18:24 ` Darrick J. Wong
2026-08-15 9:09 ` Carlos Maiolino
2026-08-17 3:09 ` 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=an9BQdSqrmzYhB3l@andromeda.toxiclabs.cc \
--to=cem@kernel.org \
--cc=aditya.ansh182@gmail.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.