Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Sun YangKai <sunk67188@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, Sun YangKai <sunk67188@gmail.com>,
	kernel test robot <lkp@intel.com>
Subject: [PATCH] btrfs: fix kernel test bot warnings
Date: Sat, 30 Aug 2025 22:40:40 +0800	[thread overview]
Message-ID: <20250830144100.3606-1-sunk67188@gmail.com> (raw)

Fixes: 2d6338c69725 ("btrfs: more trivial BTRFS_PATH_AUTO_FREE conversions")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202508301747.dZexfo9v-lkp@intel.com/
Signed-off-by: Sun YangKai <sunk67188@gmail.com>
---
 fs/btrfs/scrub.c | 2 +-
 fs/btrfs/send.c  | 2 --
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c
index d8c36cbf423d..9159e3a8af17 100644
--- a/fs/btrfs/scrub.c
+++ b/fs/btrfs/scrub.c
@@ -612,7 +612,7 @@ static void scrub_print_common_warning(const char *errstr, struct btrfs_device *
 	ret = extent_from_logical(fs_info, swarn.logical, path, &found_key,
 				  &flags);
 	if (ret < 0)
-		return ret;
+		return;
 
 	swarn.extent_item_size = found_key.offset;
 
diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c
index 6811eeb96490..69cf124674d7 100644
--- a/fs/btrfs/send.c
+++ b/fs/btrfs/send.c
@@ -1771,7 +1771,6 @@ static int gen_unique_name(struct send_ctx *sctx,
 			   u64 ino, u64 gen,
 			   struct fs_path *dest)
 {
-	int ret = 0;
 	BTRFS_PATH_AUTO_FREE(path);
 	struct btrfs_dir_item *di;
 	char tmp[64];
@@ -1806,7 +1805,6 @@ static int gen_unique_name(struct send_ctx *sctx,
 
 		if (!sctx->parent_root) {
 			/* unique */
-			ret = 0;
 			break;
 		}
 
-- 
2.50.1


             reply	other threads:[~2025-08-30 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-30 14:40 Sun YangKai [this message]
2025-08-30 21:19 ` [PATCH] btrfs: fix kernel test bot warnings David Sterba

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=20250830144100.3606-1-sunk67188@gmail.com \
    --to=sunk67188@gmail.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    /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