From: Tom Rix <trix@redhat.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: danil.kipnis@cloud.ionos.com, jinpu.wang@cloud.ionos.com,
axboe@kernel.dk, ndesaulniers@google.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] block/rnbd-clt: improve find_or_create_sess() return check
Date: Mon, 11 Jan 2021 06:49:39 -0800 [thread overview]
Message-ID: <e63aa1a6-8be6-d3b7-dbad-19b1eec287a5@redhat.com> (raw)
In-Reply-To: <20210111051431.GA4167786@ubuntu-m3-large-x86>
On 1/10/21 9:14 PM, Nathan Chancellor wrote:
> On Sun, Jan 10, 2021 at 01:57:26PM -0800, trix@redhat.com wrote:
>> From: Tom Rix <trix@redhat.com>
>>
>> clang static analysis reports this problem
>>
>> rnbd-clt.c:1212:11: warning: Branch condition evaluates to a
>> garbage value
>> else if (!first)
>> ^~~~~~
> Ah, is it complaining that the 'if (IS_ERR(sess)) {' section in
> find_or_create_sess() does not initialize first even though that will be
> caught by the 'if (sess == ERR_PTR(-ENOMEM))' in
> find_and_get_or_create_sess() because alloc_sess() only returns an
> -ENOMEM error pointer?
Reviewing the code, failure looks like it returns only -ENOMEM.
So the check is correct but brittle.
>
>> This is triggered in the find_and_get_or_create_sess() call
>> because the variable first is not initialized and the
>> earlier check is specifically for
>>
>> if (sess == ERR_PTR(-ENOMEM))
>>
>> This is false positive.
>>
>> But the if-check can be reduced by initializing first to
>> false and then returning if the call to find_or_creat_sess()
>> does not set it to true. When it remains false, either
>> sess will be valid or not. The not case is caught by
>> find_and_get_or_create_sess()'s caller rnbd_clt_map_device()
>>
>> sess = find_and_get_or_create_sess(...);
>> if (IS_ERR(sess))
>> return ERR_CAST(sess);
>>
>> Since find_and_get_or_create_sess() initializes first to false
>> setting it in find_or_create_sess() is not needed.
>>
>> Signed-off-by: Tom Rix <trix@redhat.com>
> Every maintainer has their preference for where and how stuff gets
> initialized but this makes sense to me. I am not sure the commit above
> find_or_create_sess() is needed but again, personal preference.
Mostly this removes two unneeded branches at the cost of initializing a variable.
Secondary, the static analysis complaint is resolved.
Tom
>
> Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
>
>> ---
>> drivers/block/rnbd/rnbd-clt.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/block/rnbd/rnbd-clt.c b/drivers/block/rnbd/rnbd-clt.c
>> index 96e3f9fe8241..251f747cf10d 100644
>> --- a/drivers/block/rnbd/rnbd-clt.c
>> +++ b/drivers/block/rnbd/rnbd-clt.c
>> @@ -919,6 +919,7 @@ static struct rnbd_clt_session *__find_and_get_sess(const char *sessname)
>> return NULL;
>> }
>>
>> +/* caller is responsible for initializing 'first' to false */
>> static struct
>> rnbd_clt_session *find_or_create_sess(const char *sessname, bool *first)
>> {
>> @@ -934,8 +935,7 @@ rnbd_clt_session *find_or_create_sess(const char *sessname, bool *first)
>> }
>> list_add(&sess->list, &sess_list);
>> *first = true;
>> - } else
>> - *first = false;
>> + }
>> mutex_unlock(&sess_lock);
>>
>> return sess;
>> @@ -1203,13 +1203,11 @@ find_and_get_or_create_sess(const char *sessname,
>> struct rnbd_clt_session *sess;
>> struct rtrs_attrs attrs;
>> int err;
>> - bool first;
>> + bool first = false;
>> struct rtrs_clt_ops rtrs_ops;
>>
>> sess = find_or_create_sess(sessname, &first);
>> - if (sess == ERR_PTR(-ENOMEM))
>> - return ERR_PTR(-ENOMEM);
>> - else if (!first)
>> + if (!first)
>> return sess;
>>
>> if (!path_cnt) {
>> --
>> 2.27.0
>>
next prev parent reply other threads:[~2021-01-11 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 21:57 trix
2021-01-11 5:14 ` Nathan Chancellor
2021-01-11 14:49 ` Tom Rix [this message]
2021-01-11 6:57 ` Jinpu Wang
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=e63aa1a6-8be6-d3b7-dbad-19b1eec287a5@redhat.com \
--to=trix@redhat.com \
--cc=axboe@kernel.dk \
--cc=clang-built-linux@googlegroups.com \
--cc=danil.kipnis@cloud.ionos.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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®