From: JeffleXu <jefflexu@linux.alibaba.com>
To: David Howells <dhowells@redhat.com>, Sun Ke <sunke32@huawei.com>
Cc: linux-cachefs@redhat.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] cachefiles: fix error return code in cachefiles_ondemand_copen()
Date: Wed, 24 Aug 2022 19:33:31 +0800 [thread overview]
Message-ID: <c6fd70dd-2b0b-ea9f-f0f8-9d727cde2718@linux.alibaba.com> (raw)
In-Reply-To: <3700079.1661336363@warthog.procyon.org.uk>
Hi David,
On 8/24/22 6:19 PM, David Howells wrote:
> /* fail OPEN request if copen format is invalid */
> ret = kstrtol(psize, 0, &size);
> if (ret) {
> req->error = ret;
> goto out;
> }
>
> /* fail OPEN request if daemon reports an error */
> if (size < 0) {
> if (!IS_ERR_VALUE(size))
> ret = size = -EINVAL;
> req->error = size;
> goto out;
> }
>
> Should ret get set to the error in size?
The user daemon completes the OPEN request by replying with the "copen"
command. The format of "copen" is like: "copen <id>,<cache_size>",
where <cache_size> specifies the size of the backing file. Besides,
<cache_size> is also reused for specifying the error code when the user
daemon thinks it should fail the OPEN request. In this case, the OPEN
request will fail, while the copen command (i.e.
cachefiles_ondemand_copen()) shall return 0, since the format of the
input "copen" command has no problem at all. After all, the error code
inside <cache_size> is specified by the user daemon itself, and the fact
that the OPEN request will fail totally lies in the expectation of the
user daemon.
On the other hand, cachefiles_ondemand_copen() needs to return error
code when the user daemon specifies the "copen" command in a wrong
format, e.g. specifying an invalid error code in <cache_size>. This is
exactly what this patch fixes.
--
Thanks,
Jingbo
next prev parent reply other threads:[~2022-08-24 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 12:50 Sun Ke
2022-08-19 9:18 ` [Linux-cachefs] " Gao Xiang
2022-08-20 9:22 ` JeffleXu
2022-08-24 10:19 ` David Howells
2022-08-24 11:33 ` JeffleXu [this message]
2022-08-25 13:36 ` Dan Carpenter
2022-08-25 13:58 ` [Linux-cachefs] " Gao Xiang
2022-08-26 1:11 ` Sun Ke
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=c6fd70dd-2b0b-ea9f-f0f8-9d727cde2718@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®