Re: [GIT PULL] Cgroup writeback support for 4.2

[Tejun Heo]

Hello, Geert.

On Fri, Jun 26, 2015 at 11:49:58AM +0200, Geert Uytterhoeven wrote:
> Spoiler for TLDR: These are all false positives.
> 
> If CONFIG_CGROUP_WRITEBACK=n:
> 
>     mm/page-writeback.c: In function âbalance_dirty_pages_ratelimitedâ:
>     mm/page-writeback.c:1574: warning: âwritebackâ is used
> uninitialized in this function
> 
> In this case, mem_cgroup_wb_stats() is a dummy function that doesn't
> write to its output parameters, hence writeback will contain arbitrary data.
> 
> There's another call too mem_cgroup_wb_stats() in
> wb_over_bg_thresh() where my gcc 4.1.2 didn't warn, where it probably
> deduced that mdtc will always be NULL, and the branch thus never taken.

Can you please tell me the version of gcc which triggered the above
warnings?

> Regardless of CONFIG_CGROUP_WRITEBACK:
> 
>     mm/page-writeback.c: In function âbalance_dirty_pages_ratelimitedâ:
>     mm/page-writeback.c:1537: warning: âm_bg_threshâ may be used
> uninitialized in this function
>     mm/page-writeback.c:1537: warning: âm_threshâ may be used
> uninitialized in this function
>     mm/page-writeback.c:1537: warning: âm_dirtyâ may be used
> uninitialized in this function
> 
> But these are false positives too, due to the many tests on mdtc or !mdtc,
> and the creative use of dummy *_INIT() macros and mdtc_valid() static inline
> functions.
> I suggest refactoring this code to make it less fragile, though.

It's written that way deliberately with the purpose of triggering
compile warnings if later code breaks something and code paths which
should be left out when !CGROUP_WRITEBACK aren't while not impeding
readability with ifdefs and awakwardly split dummy functions.

The hope was that most compilers in use today are smart enough to
notice the code paths which are being disabled (it's pretty darn
obvious) and it seemed that way given the dearth of build warning
reports from -next.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/