From: "Nghia Le" <nghialm78@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-safety@lists.elisa.tech
Subject: Re: [linux-safety] [PATCH] ext4/inode.c: remove dead stores in mpage_process_page()
Date: Fri, 22 Oct 2021 00:46:24 +0700 [thread overview]
Message-ID: <CADkY59vMu_MnDR3rH7EC_-wapFRELahveRQ2iHfO9oewBjCdiA@mail.gmail.com> (raw)
Message-ID: <20211021174624.m8BdZALg8Xi4Fdlxh3KIGMx0tdBU21_U--G1LyI1z-s@z> (raw)
In-Reply-To: <CAKXUXMxbLZ=y9EC9KUCCi42rO+n6ceZoPXBiMEo8ZMay=+rTeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]
Dear Lukas,
Thanks for your comments, I submitted patch v2 for the revision
Best regards,
Nghia Le
On Thu, Oct 21, 2021 at 10:57 PM Lukas Bulwahn <lukas.bulwahn@gmail.com>
wrote:
> On Thu, Oct 21, 2021 at 2:50 AM Nghia Le <nghialm78@gmail.com> wrote:
> >
> > The command "make clang-analyzer" detected dead stores.
> >
>
> Use present tense here. s/detected/detects/
>
> > Removed the all the assignments io_end_size=0 to fix dead stores, as
> > io_end_size is never read.
> >
>
> Use imperative here. So: s/Removed/Remove/
>
> drop the first "the".
>
> Maybe a better wording is:
>
> Do not reset io_end_size to 0 in the current paths, as the function
> exists on those paths without further using io_end_size.
>
> ... and the subject line could be "ext4: remove useless resetting
> io_end_size in mpage_process_page()".
>
> I hope this helps.
>
> Lukas
>
> > Signed-off-by: Nghia Le <nghialm78@gmail.com>
> > ---
> > fs/ext4/inode.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> > index 0f06305167d5..03efed2ed1ea 100644
> > --- a/fs/ext4/inode.c
> > +++ b/fs/ext4/inode.c
> > @@ -2260,7 +2260,6 @@ static int mpage_process_page(struct mpage_da_data
> *mpd, struct page *page,
> > mpd->map.m_len = 0;
> > mpd->map.m_flags = 0;
> > io_end_vec->size += io_end_size;
> > - io_end_size = 0;
> >
> > err = mpage_process_page_bufs(mpd, head, bh,
> lblk);
> > if (err > 0)
> > @@ -2285,7 +2284,6 @@ static int mpage_process_page(struct mpage_da_data
> *mpd, struct page *page,
> > } while (lblk++, (bh = bh->b_this_page) != head);
> >
> > io_end_vec->size += io_end_size;
> > - io_end_size = 0;
> > *map_bh = false;
> > out:
> > *m_lblk = lblk;
> > --
> > 2.25.1
> >
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#255): https://lists.elisa.tech/g/linux-safety/message/255
Mute This Topic: https://lists.elisa.tech/mt/86480121/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 3968 bytes --]
next prev parent reply other threads:[~2021-10-21 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 0:49 [PATCH] ext4/inode.c: remove dead stores in mpage_process_page() Nghia Le
2021-10-21 0:49 ` [linux-safety] " Nghia Le
2021-10-21 15:57 ` Lukas Bulwahn
2021-10-21 15:57 ` [linux-safety] " Lukas Bulwahn
2021-10-21 17:46 ` Nghia Le [this message]
2021-10-21 17:46 ` Nghia Le
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=CADkY59vMu_MnDR3rH7EC_-wapFRELahveRQ2iHfO9oewBjCdiA@mail.gmail.com \
--to=nghialm78@gmail.com \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@gmail.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).