public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: yangerkun <yangerkun@huawei.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>, <tytso@mit.edu>,
	<adilger.kernel@dilger.ca>, <jack@suse.cz>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: return 0 when ext4_get_group_info failed in __mb_check_buddy
Date: Tue, 2 Jan 2024 20:33:55 +0800	[thread overview]
Message-ID: <f18ffc07-aa98-4e7c-8631-88e3a62a786c@huawei.com> (raw)
In-Reply-To: <48ec32eb-145d-d6fd-e2d3-bd4a4087627b@huaweicloud.com>



在 2024/1/2 20:17, Kemeng Shi 写道:
> 
> 
> on 1/2/2024 7:20 PM, yangerkun wrote:
>> The return value for __mb_check_buddy should be a integer. Found this by
>> code review.
>>
> Hi yangerkun,
> I think the return value of __mb_check_buddy is actually not used and can
> be removed. See [1] for details :). Thanks!

Hi Kemeng,

Yeah, the return value nowdays help nothing, it's a good choice to 
remove them all.

Thanks.

> 
> [1] https://lore.kernel.org/lkml/20231125161143.3945726-2-shikemeng@huaweicloud.com/
> 
>> Fixes: 5354b2af3406 ("ext4: allow ext4_get_group_info() to fail")
>> Signed-off-by: yangerkun <yangerkun@huawei.com>
>> ---
>>   fs/ext4/mballoc.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
>> index d72b5e3c92ec..55c70a1b445a 100644
>> --- a/fs/ext4/mballoc.c
>> +++ b/fs/ext4/mballoc.c
>> @@ -758,7 +758,7 @@ static int __mb_check_buddy(struct ext4_buddy *e4b, char *file,
>>   
>>   	grp = ext4_get_group_info(sb, e4b->bd_group);
>>   	if (!grp)
>> -		return NULL;
>> +		return 0;
>>   	list_for_each(cur, &grp->bb_prealloc_list) {
>>   		ext4_group_t groupnr;
>>   		struct ext4_prealloc_space *pa;
>>
> 

      reply	other threads:[~2024-01-02 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 11:20 [PATCH] ext4: return 0 when ext4_get_group_info failed in __mb_check_buddy yangerkun
2024-01-02 12:17 ` Kemeng Shi
2024-01-02 12:33   ` yangerkun [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=f18ffc07-aa98-4e7c-8631-88e3a62a786c@huawei.com \
    --to=yangerkun@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shikemeng@huaweicloud.com \
    --cc=tytso@mit.edu \
    /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