linux-kernel - Re: [PATCH] cgroup: Fix uninitialized variable warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 28 Dec 2015 10:45:03 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Ross Zwisler <ross.zwisler@...ux.intel.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Li Zefan <lizefan@...wei.com>,
	Daniel Wagner <daniel.wagner@...-carit.de>,
	Johannes Weiner <hannes@...xchg.org>, cgroups@...r.kernel.org,
	linux-kernel@...r.kernel.org, Dave Jones <davej@...emonkey.org.uk>,
	kernel-team@...com, Aleksa Sarai <cyphar@...har.com>,
	Michal Hocko <mhocko@...nel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Neil Horman <nhorman@...driver.com>
Subject: Re: [PATCH] cgroup: Fix uninitialized variable warning

On Wed, Dec 23, 2015 at 02:53:27PM -0700, Ross Zwisler wrote:
> Commit 1f7dd3e5a6e4 ("cgroup: fix handling of multi-destination migration
> from subtree_control enabling") introduced the following compiler warning:
> 
> mm/memcontrol.c: In function ‘mem_cgroup_can_attach’:
> mm/memcontrol.c:4790:9: warning: ‘memcg’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>    mc.to = memcg;
>          ^
> 
> Fix this by initializing 'memcg' to NULL.
> 
> This was found using gcc (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6).
> 
> Signed-off-by: Ross Zwisler <ross.zwisler@...ux.intel.com>

Applied to cgroup/for-4.5.

Thanks.

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