From: Chandan Babu R <chandanbabu@kernel.org>
To: torvalds@linux-foundation.org
Cc: chandanbabu@kernel.org,aalbersh@redhat.com,djwong@kernel.org,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: bug fixes for 6.9
Date: Sat, 06 Apr 2024 18:02:40 +0530 [thread overview]
Message-ID: <878r1q3byi.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Linus,
Please pull this branch which contains an XFS bug fix for 6.9-rc3. A brief
summary 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 39cd87c4eb2b893354f3b850f916353f2658ae6f:
Linux 6.9-rc2 (2024-03-31 14:32:39 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.9-fixes-2
for you to fetch changes up to e23d7e82b707d1d0a627e334fb46370e4f772c11:
xfs: allow cross-linking special files without project quota (2024-04-01 11:55:49 +0530)
----------------------------------------------------------------
Bug fixes for 6.9-rc3:
* Allow creating new links to special files which were not associated with a
project quota.
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
----------------------------------------------------------------
Andrey Albershteyn (1):
xfs: allow cross-linking special files without project quota
fs/xfs/xfs_inode.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
next reply other threads:[~2024-04-06 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 12:32 Chandan Babu R [this message]
2024-04-06 16:19 ` [GIT PULL] xfs: bug fixes for 6.9 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-03-30 13:49 [GIT PULL] xfs: Bug " Chandan Babu R
2024-03-30 20:54 ` pr-tracker-bot
2024-03-22 13:32 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=878r1q3byi.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=aalbersh@redhat.com \
--cc=djwong@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).