From: Chao Yu <yuchao0@huawei.com> To: Jason Yan <yanaijie@huawei.com>, <jaegeuk@kernel.org>, <chao@kernel.org>, <linux-f2fs-devel@lists.sourceforge.net>, <linux-kernel@vger.kernel.org> Cc: Kees Cook <keescook@chromium.org>, <kernel-hardening@lists.openwall.com> Subject: Re: [f2fs-dev] [PATCH] f2fs: Eliminate usage of uninitialized_var() macro Date: Mon, 15 Jun 2020 16:26:25 +0800 [thread overview] Message-ID: <d1562b04-125f-c112-7272-d99ed1e38549@huawei.com> (raw) In-Reply-To: <20200615040212.3681503-1-yanaijie@huawei.com> On 2020/6/15 12:02, Jason Yan wrote: > This is an effort to eliminate the uninitialized_var() macro[1]. > > The use of this macro is the wrong solution because it forces off ANY > analysis by the compiler for a given variable. It even masks "unused > variable" warnings. > > Quoted from Linus[2]: > > "It's a horrible thing to use, in that it adds extra cruft to the > source code, and then shuts up a compiler warning (even the _reliable_ > warnings from gcc)." > > The gcc option "-Wmaybe-uninitialized" has been disabled and this change > will not produce any warnnings even with "make W=1". > > [1] https://github.com/KSPP/linux/issues/81 > [2] https://lore.kernel.org/lkml/CA+55aFz2500WfbKXAx8s67wrm9=yVJu65TpLgN_ybYNv0VEOKA@mail.gmail.com/ > > Cc: Kees Cook <keescook@chromium.org> > Signed-off-by: Jason Yan <yanaijie@huawei.com> > --- > fs/f2fs/data.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > index 326c63879ddc..e6ec61274d76 100644 > --- a/fs/f2fs/data.c > +++ b/fs/f2fs/data.c > @@ -2856,7 +2856,7 @@ static int f2fs_write_cache_pages(struct address_space *mapping, > }; > #endif > int nr_pages; > - pgoff_t uninitialized_var(writeback_index); > + pgoff_t writeback_index; I suggest to delete this variable directly, as we did for mm in commit 28659cc8cc87 (mm/page-writeback.c: remove unused variable). Thanks, > pgoff_t index; > pgoff_t end; /* Inclusive */ > pgoff_t done_index; >
next prev parent reply other threads:[~2020-06-15 8:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-15 4:02 Jason Yan 2020-06-15 8:26 ` Chao Yu [this message] 2020-06-15 8:38 ` [f2fs-dev] " Jason Yan
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=d1562b04-125f-c112-7272-d99ed1e38549@huawei.com \ --to=yuchao0@huawei.com \ --cc=chao@kernel.org \ --cc=jaegeuk@kernel.org \ --cc=keescook@chromium.org \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=yanaijie@huawei.com \ --subject='Re: [f2fs-dev] [PATCH] f2fs: Eliminate usage of uninitialized_var() macro' \ /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
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).