[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d40a1e7e-d78c-1a99-0889-6fc4d2102e9d@huawei.com>
Date: Wed, 17 Aug 2022 09:44:46 +0800
From: Sun Ke <sunke32@...wei.com>
To: Gao Xiang <hsiangkao@...ux.alibaba.com>
CC: <xiang@...nel.org>, <chao@...nel.org>,
<linux-erofs@...ts.ozlabs.org>, <linux-kernel@...r.kernel.org>,
<kernel-janitors@...r.kernel.org>, <yinxin.x@...edance.com>
Subject: Re: [PATCH] erofs: fix error return code in
erofs_fscache_meta_read_folio and erofs_fscache_read_folio
在 2022/8/16 13:16, Gao Xiang 写道:
> On Mon, Aug 15, 2022 at 11:48:29AM +0800, Sun Ke wrote:
>> If erofs_fscache_alloc_request fail and then goto out, it will return 0.
>> it should return a negative error code instead of 0.
>>
>> Fixes: d435d53228dd ("erofs: change to use asynchronous io for fscache readpage/readahead")
>> Signed-off-by: Sun Ke <sunke32@...wei.com>
>
> Minor, I tried to apply this patch by updating the patch title into
> "erofs: fix error return code in erofs_fscache_{meta_,}read_folio"
>
> since the original patch title is too long.
Should I send a v2 patch to update the title?
Thanks,
Sun Ke
>
> Thanks,
> Gao Xiang
> .
>
Powered by blists - more mailing lists