From: Dan Carpenter <dan.carpenter@oracle.com>
To: JeffleXu <jefflexu@linux.alibaba.com>
Cc: David Howells <dhowells@redhat.com>, Sun Ke <sunke32@huawei.com>,
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: Thu, 25 Aug 2022 16:36:20 +0300 [thread overview]
Message-ID: <20220825133620.GB2071@kadam> (raw)
In-Reply-To: <c6fd70dd-2b0b-ea9f-f0f8-9d727cde2718@linux.alibaba.com>
I spent a long time looking at this as well... It's really inscrutable
code. It would be more readable if we just spelled things out in the
most pedantic way possible:
diff --git a/fs/cachefiles/ondemand.c b/fs/cachefiles/ondemand.c
index 1fee702d5529..7e1586bd5cf3 100644
--- a/fs/cachefiles/ondemand.c
+++ b/fs/cachefiles/ondemand.c
@@ -158,9 +158,13 @@ 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;
- req->error = size;
+ if (!IS_ERR_VALUE(size)) {
+ req->error = -EINVAL;
+ ret = -EINVAL;
+ } else {
+ req->error = size;
+ ret = 0;
+ }
goto out;
}
next prev parent reply other threads:[~2022-08-25 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 12:50 [PATCH v3] cachefiles: fix error return code in cachefiles_ondemand_copen() 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
2022-08-25 13:36 ` Dan Carpenter [this message]
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=20220825133620.GB2071@kadam \
--to=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=jefflexu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).