mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Naohiro Aota <Naohiro.Aota@wdc.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: zoned: Remove some code duplication
Date: Thu, 20 Feb 2025 05:55:14 +0000	[thread overview]
Message-ID: <D7X1HAEVN3TO.Z7JG9SRUODCE@wdc.com> (raw)
In-Reply-To: <74072f83285f96aba98add7d24c9f944d22a721b.1739974151.git.christophe.jaillet@wanadoo.fr>

On Wed Feb 19, 2025 at 11:10 PM JST, Christophe JAILLET wrote:
> This code snippet is written twice in row, so remove one of them.
>
> This was apparently added by accident in commit efe28fcf2e47 ("btrfs:
> handle unexpected parent block offset in btrfs_alloc_tree_block()")
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
>  fs/btrfs/zoned.c | 9 ---------
>  1 file changed, 9 deletions(-)
>
> diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
> index b5b9d16664a8..6c4534316aad 100644
> --- a/fs/btrfs/zoned.c
> +++ b/fs/btrfs/zoned.c
> @@ -1663,15 +1663,6 @@ int btrfs_load_block_group_zone_info(struct btrfs_block_group *cache, bool new)
>  	}
>  
>  out:
> -	/* Reject non SINGLE data profiles without RST */
> -	if ((map->type & BTRFS_BLOCK_GROUP_DATA) &&
> -	    (map->type & BTRFS_BLOCK_GROUP_PROFILE_MASK) &&
> -	    !fs_info->stripe_root) {
> -		btrfs_err(fs_info, "zoned: data %s needs raid-stripe-tree",
> -			  btrfs_bg_type_to_raid_name(map->type));
> -		return -EINVAL;
> -	}
> -
>  	/* Reject non SINGLE data profiles without RST. */
>  	if ((map->type & BTRFS_BLOCK_GROUP_DATA) &&
>  	    (map->type & BTRFS_BLOCK_GROUP_PROFILE_MASK) &&

Thanks, but which repository/branch are you working with? I cannot
find the duplicated lines in btrfs/for-next, linus/master, nor
linux-stable. Also, the pointed commit seems wrong too.

  reply	other threads:[~2025-02-20  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 14:10 Christophe JAILLET
2025-02-20  5:55 ` Naohiro Aota [this message]
2025-02-20  7:11   ` Christophe JAILLET
2025-02-26 15:20     ` 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=D7X1HAEVN3TO.Z7JG9SRUODCE@wdc.com \
    --to=naohiro.aota@wdc.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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 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®