From: Thorsten Blum <thorsten.blum@linux.dev>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcachefs: Remove duplicate condition in return statement
Date: Sat, 22 Feb 2025 15:16:29 +0100 [thread overview]
Message-ID: <0FD94900-D786-4DB2-A5D4-B6B723A940E7@linux.dev> (raw)
In-Reply-To: <f7zphgeldym3m6rdlygmfrzwlgpdqzptvv2bwrq2jotpt2yadp@y7vck65ft3qy>
On 22. Feb 2025, at 15:05, Kent Overstreet wrote:
> On Sat, Feb 22, 2025 at 02:31:01PM +0100, Thorsten Blum wrote:
>> The last two conditions in the return statement are identical. Remove
>> one of them.
>>
>> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>> ---
>> fs/bcachefs/extents.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/fs/bcachefs/extents.h b/fs/bcachefs/extents.h
>> index 620b284aa34f..8afcf2c75015 100644
>> --- a/fs/bcachefs/extents.h
>> +++ b/fs/bcachefs/extents.h
>> @@ -703,7 +703,6 @@ static inline bool bch2_extent_ptr_eq(struct bch_extent_ptr ptr1,
>> return (ptr1.cached == ptr2.cached &&
>> ptr1.unwritten == ptr2.unwritten &&
>> ptr1.offset == ptr2.offset &&
>> - ptr1.dev == ptr2.dev &&
>> ptr1.dev == ptr2.dev);
>>
> Actually should have been checking gen:
>
>
> From b0e5e78f7e890c48b69e24d19e82597daa2d9cf0 Mon Sep 17 00:00:00 2001
> From: Kent Overstreet <kent.overstreet@linux.dev>
> Date: Sat, 22 Feb 2025 09:05:36 -0500
> Subject: [PATCH] bcachefs: fix bch2_extent_ptr_eq()
>
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> diff --git a/fs/bcachefs/extents.h b/fs/bcachefs/extents.h
> index 8fae6b23a341..ed160aaa9546 100644
> --- a/fs/bcachefs/extents.h
> +++ b/fs/bcachefs/extents.h
> @@ -704,7 +704,7 @@ static inline bool bch2_extent_ptr_eq(struct bch_extent_ptr ptr1,
> ptr1.unwritten == ptr2.unwritten &&
> ptr1.offset == ptr2.offset &&
> ptr1.dev == ptr2.dev &&
> - ptr1.dev == ptr2.dev);
> + ptr1.gen == ptr2.gen);
> }
>
> void bch2_ptr_swab(struct bkey_s);
Thanks, I was about to ask if it should have been gen instead.
Feel free to add:
Reviewed-by: Thorsten Blum <thorsten.blum@linux.dev>
prev parent reply other threads:[~2025-02-22 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 13:31 [PATCH] bcachefs: Remove duplicate condition in return statement Thorsten Blum
2025-02-22 14:05 ` Kent Overstreet
2025-02-22 14:16 ` Thorsten Blum [this message]
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=0FD94900-D786-4DB2-A5D4-B6B723A940E7@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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;
as well as URLs for NNTP newsgroup(s).