From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yang Shi <yang.shi@linaro.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] writeback: initialize m_dirty to avoid compile warning
Date: Wed, 18 Nov 2015 13:11:42 -0500 [thread overview]
Message-ID: <20151118181142.GC11496@mtj.duckdns.org> (raw)
In-Reply-To: <20151117153855.99d2acd0568d146c29defda5@linux-foundation.org>
Hello,
On Tue, Nov 17, 2015 at 03:38:55PM -0800, Andrew Morton wrote:
> > --- a/mm/page-writeback.c
> > +++ b/mm/page-writeback.c
> > @@ -1542,7 +1542,7 @@ static void balance_dirty_pages(struct address_space *mapping,
> > for (;;) {
> > unsigned long now = jiffies;
> > unsigned long dirty, thresh, bg_thresh;
> > - unsigned long m_dirty, m_thresh, m_bg_thresh;
> > + unsigned long m_dirty = 0, m_thresh = 0, m_bg_thresh = 0;
> >
> > /*
> > * Unstable writes are a feature of certain networked
>
> Adding runtime overhead to suppress a compile-time warning is Just
> Wrong.
>
> With gcc-4.4.4 the above patch actually reduces page-writeback.o's
> .text by 36 bytes, lol. With gcc-4.8.4 the patch saves 19 bytes. No
> idea what's going on there...
>
>
> And initializing locals in the above fashion can hide real bugs -
> looky:
This was the main reason the code was structured the way it is. If
cgroup writeback is not enabled, any derefs of mdtc variables should
trigger warnings. Ugh... I don't know. Compiler really should be
able to tell this much.
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-11-18 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 18:26 Yang Shi
2015-11-17 23:38 ` Andrew Morton
2015-11-18 9:53 ` Arnd Bergmann
2015-11-18 17:32 ` Shi, Yang
2015-11-18 18:11 ` Tejun Heo [this message]
2015-11-18 18:27 ` Shi, Yang
2015-11-18 18:33 ` Tejun Heo
2015-11-18 18:39 ` Shi, Yang
2015-11-18 18:55 ` Andrew Morton
2015-11-18 18:57 ` Shi, Yang
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=20151118181142.GC11496@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yang.shi@linaro.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