All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Orzel <michalorzel.eng@gmail.com>
To: Tom Rix <trix@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	"Richard Russon (FlatCap)" <ldm@flatcap.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net, llvm@lists.linux.dev
Subject: Re: [PATCH] block: Remove redundant assignments
Date: Tue, 12 Apr 2022 17:23:57 +0200	[thread overview]
Message-ID: <1c8fa321-d91e-c906-a7da-c252a112191b@gmail.com> (raw)
In-Reply-To: <c2c40f00-777c-f19a-eb5f-6e978ddd6bcf@redhat.com>

Hi Tom,

On 09.04.2022 18:03, Tom Rix wrote:
> 
> On 4/9/22 6:20 AM, Michal Orzel wrote:
>> Hi Tom,
>>
>>> On 4/9/22 3:19 AM, Michal Orzel wrote:
>>>> Get rid of redundant assignments which end up in values not being
>>>> read either because they are overwritten or the function ends.
>>> This log is the same as your last patch.
>>>
>>> Instead of a general statement on deadstores, a more specific
>>>
>>> analysis of the setting being removed would be helpful.
>>>
>>> This will mean splitting the patch to match the analysis.
>>>
>>> Tom
>>>
>> I think that this explanation in a commit is enough for such a trivial patch.
>> It informs that we are fixing clang-tidy findings related to deadstores
>> in a block subsystem. What analysis would you want to see?
>> Something like "Remove deadstore assignment ret = -EINVAL  in a function bio_map_user_iov" ?
>> I think that it will create too much of not needed overhead.
> 
> The compiler should remove these already.  All of the static analyzers produce false positives, if you do not provide analysis the reviewer has to assume you have not done any and has to do the false positive analysis themselves. This burdens the reviewer for something of small value that can be dismissed as churn.
> 
> Tom
> 

Ok, I will split the patch into series in v2 and I will add some analysis into commit msg.

Cheers,
Michal

  reply	other threads:[~2022-04-12 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 10:19 [PATCH] ipc/sem: Remove redundant assignments Michal Orzel
2022-04-09 10:19 ` [PATCH] block: " Michal Orzel
2022-04-09 12:01   ` Tom Rix
2022-04-09 13:20     ` Michal Orzel
2022-04-09 16:03       ` Tom Rix
2022-04-12 15:23         ` Michal Orzel [this message]
2022-04-09 11:47 ` [PATCH] ipc/sem: " Tom Rix
2022-04-11 15:47 ` Nathan Chancellor
2022-04-12 15:19   ` Michal Orzel

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=1c8fa321-d91e-c906-a7da-c252a112191b@gmail.com \
    --to=michalorzel.eng@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=ldm@flatcap.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.