From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: fix a missing unlock in xfs_growfs_data
Date: Mon, 24 Mar 2025 09:52:09 +0100 [thread overview]
Message-ID: <174280632955.284683.5178000607075767414.b4-ty@kernel.org> (raw)
In-Reply-To: <20250317054512.1131950-2-hch@lst.de>
On Mon, 17 Mar 2025 06:44:52 +0100, Christoph Hellwig wrote:
> The newly added check for the internal RT device needs to unlock
> m_growlock just like all ther other error cases.
>
>
Applied to for-next, thanks!
[1/3] xfs: fix a missing unlock in xfs_growfs_data
commit: beba9487138151c17dec17105364b35935f21562
[2/3] xfs: don't increment m_generation for all errors in xfs_growfs_data
commit: 9ec3f7977a32f2045ef14445f165bcd96e596344
[3/3] xfs: don't wake zone space waiters without m_zone_info
commit: f56f73ebf8bb13d72b93e490c1f175a0a2c836f2
Best regards,
--
Carlos Maiolino <cem@kernel.org>
next prev parent reply other threads:[~2025-03-24 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 5:44 zoned fixes Christoph Hellwig
2025-03-17 5:44 ` [PATCH 1/3] xfs: fix a missing unlock in xfs_growfs_data Christoph Hellwig
2025-03-18 11:54 ` Carlos Maiolino
2025-03-24 8:52 ` Carlos Maiolino [this message]
2025-03-17 5:44 ` [PATCH 2/3] xfs: don't increment m_generation for all errors " Christoph Hellwig
2025-03-18 12:01 ` Carlos Maiolino
2025-03-17 5:44 ` [PATCH 3/3] xfs: don't wake zone space waiters without m_zone_info Christoph Hellwig
2025-03-17 14:46 ` Hans Holmberg
2025-03-18 12:04 ` 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=174280632955.284683.5178000607075767414.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=djwong@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--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