From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Anand Jain <anand.jain@oracle.com>,
David Sterba <dsterba@suse.com>, Sasha Levin <sashal@kernel.org>
Subject: [PATCH 5.15.y 1/4] btrfs: rename ret to err in btrfs_recover_relocation()
Date: Sun, 6 Sep 2026 12:18:18 -0400 [thread overview]
Message-ID: <20260906161821.1555270-1-sashal@kernel.org> (raw)
In-Reply-To: <2026090359-pebble-underpaid-4ffa@gregkh>
From: Anand Jain <anand.jain@oracle.com>
[ Upstream commit ba69f42af2a568f30904a11dc257eb892c5e8c0e ]
In the function btrfs_recover_relocation(), currently the variable 'err'
carries the return value and 'ret' holds the intermediary return value.
However, in some lines, we don't need this two-step approach; we can
directly use 'err'. So, optimize them, which requires reinitializing 'err'
to zero at two locations.
This is a preparatory patch to fix the code style by renaming 'err'
to 'ret'.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Stable-dep-of: 6d8ba4572922 ("btrfs: drop recovered reloc root refs on recovery failure")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/btrfs/relocation.c | 28 +++++++++++-----------------
1 file changed, 11 insertions(+), 17 deletions(-)
diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
index 06cf946834017..8e465849c26c3 100644
--- a/fs/btrfs/relocation.c
+++ b/fs/btrfs/relocation.c
@@ -4220,17 +4220,16 @@ int btrfs_recover_relocation(struct btrfs_root *root)
key.offset = (u64)-1;
while (1) {
- ret = btrfs_search_slot(NULL, fs_info->tree_root, &key,
+ err = btrfs_search_slot(NULL, fs_info->tree_root, &key,
path, 0, 0);
- if (ret < 0) {
- err = ret;
+ if (err < 0)
goto out;
- }
- if (ret > 0) {
+ if (err > 0) {
if (path->slots[0] == 0)
break;
path->slots[0]--;
}
+ err = 0;
leaf = path->nodes[0];
btrfs_item_key_to_cpu(leaf, &key, path->slots[0]);
btrfs_release_path(path);
@@ -4252,16 +4251,13 @@ int btrfs_recover_relocation(struct btrfs_root *root)
fs_root = btrfs_get_fs_root(fs_info,
reloc_root->root_key.offset, false);
if (IS_ERR(fs_root)) {
- ret = PTR_ERR(fs_root);
- if (ret != -ENOENT) {
- err = ret;
+ err = PTR_ERR(fs_root);
+ if (err != -ENOENT)
goto out;
- }
- ret = mark_garbage_root(reloc_root);
- if (ret < 0) {
- err = ret;
+ err = mark_garbage_root(reloc_root);
+ if (err < 0)
goto out;
- }
+ err = 0;
} else {
btrfs_put_root(fs_root);
}
@@ -4283,11 +4279,9 @@ int btrfs_recover_relocation(struct btrfs_root *root)
goto out;
}
- ret = reloc_chunk_start(fs_info);
- if (ret < 0) {
- err = ret;
+ err = reloc_chunk_start(fs_info);
+ if (err < 0)
goto out_end;
- }
rc->extent_root = fs_info->extent_root;
--
2.53.0
next prev parent reply other threads:[~2026-09-06 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 13:23 FAILED: patch "[PATCH] btrfs: drop recovered reloc root refs on recovery failure" failed to apply to 5.15-stable tree gregkh
2026-09-06 16:18 ` Sasha Levin [this message]
2026-09-06 16:18 ` [PATCH 5.15.y 2/4] btrfs: rename ret to ret2 in btrfs_recover_relocation() Sasha Levin
2026-09-06 16:18 ` [PATCH 5.15.y 3/4] btrfs: rename err to ret " Sasha Levin
2026-09-06 16:18 ` [PATCH 5.15.y 4/4] btrfs: drop recovered reloc root refs on recovery failure Sasha Levin
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=20260906161821.1555270-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.