From: Chandan Babu R <chandanbabu@kernel.org>
To: torvalds@linux-foundation.org
Cc: chandanbabu@kernel.org, dchinner@redhat.com, djwong@kernel.org,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, mark.tinguely@oracle.com
Subject: [GIT PULL] xfs: Bug fixes for 6.9
Date: Sat, 30 Mar 2024 19:19:34 +0530 [thread overview]
Message-ID: <875xx3lta0.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Linus,
Please pull this branch which contains two XFS bug fixes for 6.9-rc2. A brief
summary of the bug fixes is provided below.
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 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.9-fixes-1
for you to fetch changes up to f2e812c1522dab847912309b00abcc762dd696da:
xfs: don't use current->journal_info (2024-03-25 10:21:01 +0530)
----------------------------------------------------------------
Bug fixes for 6.9-rc2:
* Allow stripe unit/width value passed via mount option to be written over
existing values in the super block.
* Do not set current->journal_info to avoid its value from being miused by
another filesystem context.
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
----------------------------------------------------------------
Dave Chinner (2):
xfs: allow sunit mount option to repair bad primary sb stripe values
xfs: don't use current->journal_info
fs/xfs/libxfs/xfs_sb.c | 40 +++++++++++++++++++++++++++++++---------
fs/xfs/libxfs/xfs_sb.h | 5 +++--
fs/xfs/scrub/common.c | 4 +---
fs/xfs/xfs_aops.c | 7 -------
fs/xfs/xfs_icache.c | 8 +++++---
fs/xfs/xfs_trans.h | 9 +--------
6 files changed, 41 insertions(+), 32 deletions(-)
next reply other threads:[~2024-03-30 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 13:49 Chandan Babu R [this message]
2024-03-30 20:54 ` [GIT PULL] xfs: Bug fixes for 6.9 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-04-06 12:32 [GIT PULL] xfs: bug " Chandan Babu R
2024-04-06 16:19 ` pr-tracker-bot
2024-03-22 13:32 [GIT PULL] xfs: Bug " Chandan Babu R
2024-03-22 18:17 ` 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=875xx3lta0.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mark.tinguely@oracle.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).