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 fix for 6.10
Date: Sat, 15 Jun 2024 21:30:28 +0530 [thread overview]
Message-ID: <871q4yfb08.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Linus,
Please pull this branch which contains an XFS bug fix for 6.10-rc4. A brief
description of the bug fix 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 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git xfs-6.10-fixes-3
for you to fetch changes up to 58f880711f2ba53fd5e959875aff5b3bf6d5c32e:
xfs: make sure sb_fdblocks is non-negative (2024-06-10 11:38:12 +0530)
----------------------------------------------------------------
Bug fixes for 6.10-rc4:
* Ensure xfs incore superblock's
1. Allocated inode counter
2. Free inode counter
3. Free data block counter
are zero or positive when they are copied over from
xfs_mount->m_[icount,ifree,fdblocks] respectively.
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
----------------------------------------------------------------
Wengang Wang (1):
xfs: make sure sb_fdblocks is non-negative
fs/xfs/libxfs/xfs_sb.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
next reply other threads:[~2024-06-15 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 16:00 Chandan Babu R [this message]
2024-06-15 19:15 ` [GIT PULL] xfs: bug fix for 6.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-06-22 13:35 Chandan Babu R
2024-06-22 16:00 ` Darrick J. Wong
2024-06-22 16:04 ` Linus Torvalds
2024-06-22 16:05 ` Darrick J. Wong
2024-06-22 16:08 ` Linus Torvalds
2024-06-22 16:10 ` 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=871q4yfb08.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