From: Sukrut Heroorkar <hsukrut3@gmail.com>
To: Jan Kara <jack@suse.com>, linux-kernel@vger.kernel.org (open list)
Cc: shuah@kernel.org, david.hunter.linux@gmail.com,
Sukrut Heroorkar <hsukrut3@gmail.com>
Subject: [PATCH 6.1.y 0/2] udf: backport udf_rename fixes to verify link-count
Date: Tue, 25 Nov 2025 16:33:26 +0530 [thread overview]
Message-ID: <cover.1763999341.git.hsukrut3@gmail.com> (raw)
This series backports two upstream commits needed to fix a udf_rename
crash reported by syzbot.
https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
Patch 1: brings in the prerequisite restructuring of udf_rename from
upstream commit 9d35cebb794b ("udf_rename(): only access the child content
on cross-directory rename"). This commit introduces is_dir that the later
fix depends upon.
Patch 2: backports upstream commit 6756af923e06 ("udf: Verify inode link
counts before performing rename"), which adds the link-count verifications.
Both the patches apply cleanly to v6.1.y and this upstream fix is already
backported to v6.12.y with commit id 0a65d850c45d and, to v6.6.y with commit id
b41d73055284.
The reproducer from syzbot no longer triggers issue with this series
applied. The patch containing diffs, combined from both the commit was
tested by syzbot and it triggers no issue. The kernel also builds &
boots on a native x86_64 machine with this fix applied.
Al Viro (1):
udf_rename(): only access the child content on cross-directory rename
Jan Kara (1):
udf: Verify inode link counts before performing rename
fs/udf/namei.c | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-11-25 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 11:03 Sukrut Heroorkar [this message]
2025-11-25 11:03 ` [PATCH 6.1.y 1/2] udf_rename(): only access the child content on cross-directory rename Sukrut Heroorkar
2025-11-25 11:03 ` [PATCH 6.1.y 2/2] udf: Verify inode link counts before performing rename Sukrut Heroorkar
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=cover.1763999341.git.hsukrut3@gmail.com \
--to=hsukrut3@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@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