From: Chandan Babu R <chandanbabu@kernel.org>
To: torvalds@linux-foundation.org
Cc: chandanbabu@kernel.org,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: bug fixes for 6.8
Date: Sat, 27 Jan 2024 16:52:58 +0530 [thread overview]
Message-ID: <87sf2j2f2t.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Linus,
Please pull this branch with changes for xfs for 6.8-rc2. The changes are
limited to just one bug fix.
I did a test-merge with the main upstream branch as of a few minutes ago and
didn't see any conflicts. Please let me know if you encounter any problems.
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.8-fixes-1
for you to fetch changes up to d8d222e09dab84a17bb65dda4b94d01c565f5327:
xfs: read only mounts with fsopen mount API are busted (2024-01-22 11:33:57 +0530)
----------------------------------------------------------------
Bug fixes for 6.8-rc2:
* Fix read only mounts when using fsopen mount API
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
----------------------------------------------------------------
Dave Chinner (1):
xfs: read only mounts with fsopen mount API are busted
fs/xfs/xfs_super.c | 27 +++++++++++++++++----------
1 file changed, 17 insertions(+), 10 deletions(-)
next reply other threads:[~2024-01-27 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 11:22 Chandan Babu R [this message]
2024-01-27 17:21 ` [GIT PULL] xfs: bug fixes for 6.8 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-03 15:22 Chandan Babu R
2024-02-04 7:44 ` pr-tracker-bot
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=87sf2j2f2t.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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