From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Yangtao Li <frank.li@vivo.com>, <jaegeuk@kernel.org>, <chao@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH REPOST] f2fs: file: drop useless initializer in expand_inode_data()
Date: Wed, 21 Dec 2022 17:46:10 +0300 [thread overview]
Message-ID: <07bca981-edb0-aa85-28e2-ceaf58b6a519@omp.ru> (raw)
In-Reply-To: <20221221033021.36615-1-frank.li@vivo.com>
Hello!
On 12/21/22 6:30 AM, Yangtao Li wrote:
>> In expand_inode_data(), the 'new_size' local variable is initialized to
>> the result of i_size_read(), however this value isn't ever used, so we
>> can drop this initializer...
>>
>> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
>> analysis tool.
>>
>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>
>> ---
>> This patch is against the 'dev' branch of Jaegeuk Kim's F2FS repo...
>> Reposting with ISP RAS mailing lists CC'ed now...
>
> Why do you repeatedly send a patch that cannot be applied,
Why (it does apply to your 'dev' branch)? Because of the merge window?
> and this does not have a CC on linux-kernel.vger.kernel.org.
I normnally avoid CCing LKML as my patches are not generally interesting
to the wide public (I think)...
> Otherwise, code modification looks good to me.
Thanx!
> Thx,
> Yangtao
MBR, Sergey
next prev parent reply other threads:[~2022-12-21 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 3:30 Yangtao Li
2022-12-21 12:34 ` Chao Yu
2022-12-21 14:55 ` Sergey Shtylyov
2022-12-21 14:46 ` Sergey Shtylyov [this message]
2022-12-21 14:50 ` Sergey Shtylyov
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=07bca981-edb0-aa85-28e2-ceaf58b6a519@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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®