From: JeffleXu <jefflexu@linux.alibaba.com>
To: Sun Ke <sunke32@huawei.com>, dhowells@redhat.com
Cc: linux-cachefs@redhat.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [v2] cachefiles: fix error return code in cachefiles_ondemand_copen()
Date: Thu, 18 Aug 2022 20:15:37 +0800 [thread overview]
Message-ID: <b98cb85c-cac2-9117-12fd-570d246b20d3@linux.alibaba.com> (raw)
In-Reply-To: <adf4b4c2-75a2-705d-8870-df130fb583fb@huawei.com>
On 8/18/22 7:27 PM, Sun Ke wrote:
>
>
> 在 2022/8/18 19:14, JeffleXu 写道:
>>
>>
>> On 8/18/22 7:19 PM, Sun Ke wrote:
>>> If size < 0; open request will fail, but cachefiles_ondemand_copen
>>> return 0.
>>> Fix to return a negative error code.
>>
>> Could you please also update the commit log?
>
> The cache_size field of copen is specified by the user daemon. If
> cache_size < 0, then the OPEN request is expected to fail, while copen
> itself shall succeed. However, return 0 is indeed unexpected when
^
returning
> cache_size is an invalid error code.
> Fix to return a negative error code.
Fix this by returning error when cache_size is an invalid error code.
>>
>> Otherwise LGTM.
>>
>> Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
>>
>>
>> BTW, also cc linux-fsdevel@vger.kernel.org
>>
>>>
>>> Fixes: c8383054506c ("cachefiles: notify the user daemon when looking
>>> up cookie")
>>> Signed-off-by: Sun Ke <sunke32@huawei.com>
>>> ---
>>> fs/cachefiles/ondemand.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/cachefiles/ondemand.c b/fs/cachefiles/ondemand.c
>>> index 1fee702d5529..ea8a1e8317d9 100644
>>> --- a/fs/cachefiles/ondemand.c
>>> +++ b/fs/cachefiles/ondemand.c
>>> @@ -159,7 +159,7 @@ int cachefiles_ondemand_copen(struct
>>> cachefiles_cache *cache, char *args)
>>> /* fail OPEN request if daemon reports an error */
>>> if (size < 0) {
>>> if (!IS_ERR_VALUE(size))
>>> - size = -EINVAL;
>>> + ret = size = -EINVAL;
>>> req->error = size;
>>> goto out;
>>> }
>>
--
Thanks,
Jingbo
prev parent reply other threads:[~2022-08-18 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 11:19 Sun Ke
2022-08-18 11:14 ` JeffleXu
2022-08-18 11:27 ` Sun Ke
2022-08-18 12:15 ` JeffleXu [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=b98cb85c-cac2-9117-12fd-570d246b20d3@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunke32@huawei.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
all inboxes | Powered by JetHome®