From: Burenchev Evgenii <EBurenchev@orionsoft.ru>
To: "clm@fb.com" <clm@fb.com>, "dsterba@suse.com" <dsterba@suse.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: [PATCH] btrfs: remove dead assignment to dirid in btrfs_search_path_in_tree()
Date: Mon, 16 Feb 2026 16:16:53 +0000 [thread overview]
Message-ID: <3f1d7281b3004c6baa24a531b409c466@orionsoft.ru> (raw)
From ff2df73ba6483b0dc67b3ed89d2a43c49f1c2eb8 Mon Sep 17 00:00:00 2001
From: Evgenii Burenchev <eburenchev@orionsoft.ru>
Date: Mon, 16 Feb 2026 18:39:30 +0300
Subject: [PATCH] btrfs: remove dead assignment to dirid in
btrfs_search_path_in_tree()
After the introduction of btrfs_search_backwards(), the directory
traversal state in btrfs_search_path_in_tree() is fully maintained via
struct btrfs_key. The local variable 'dirid' is no longer used to control
the search and the assignment
dirid = key.objectid;
has no observable effect and is dead code.
Remove the unused assignment to avoid confusion and silence static
analysis warnings.
No functional change.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Signed-off-by: Evgenii Burenchev <eburenchev@orionsoft.ru>
---
fs/btrfs/ioctl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index a6cc2d3b414c..292043b11207 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -1708,7 +1708,6 @@ static noinline int btrfs_search_path_in_tree(struct btrfs_fs_info *info,
btrfs_release_path(path);
key.objectid = key.offset;
key.offset = (u64)-1;
- dirid = key.objectid;
}
memmove(name, ptr, total_len);
name[total_len] = '\0';
--
2.43.0
next reply other threads:[~2026-02-16 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:16 Burenchev Evgenii [this message]
2026-02-17 9:37 ` Fedor Pchelkin
2026-02-17 10:17 ` Miquel Sabaté Solà
[not found] ` <6994405b.170a0220.24287.89ffSMTPIN_ADDED_BROKEN@mx.google.com>
2026-02-17 10:53 ` Filipe Manana
2026-02-17 11:23 ` Miquel Sabaté Solà
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=3f1d7281b3004c6baa24a531b409c466@orionsoft.ru \
--to=eburenchev@orionsoft.ru \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.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
all inboxes | Powered by JetHome®