oprofile, s390: Fix uninitialized memory access when writing to oprofilefs
authorRobert Richter <robert.richter@amd.com>
Thu, 19 Jul 2012 16:28:26 +0000 (18:28 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 2 Oct 2012 17:29:55 +0000 (10:29 -0700)
commit93ee70835a254181a9d9c5750e9301b70899ad90
treee6b82ddb5bf1ce512d86a7c5c9afe84629743809
parentd409354d1b8a1e47b8f29887179949ec951ffe83
oprofile, s390: Fix uninitialized memory access when writing to oprofilefs

commit 81ff3478d9ba7f0b48b0abef740e542fd83adf79 upstream.

If oprofilefs_ulong_from_user() is called with count equals zero, *val
remains unchanged. Depending on the implementation it might be
uninitialized. Fixing users of oprofilefs_ulong_ from_user().

We missed these s390 changes with:

 913050b oprofile: Fix uninitialized memory access when writing to writing to oprofilefs

Signed-off-by: Robert Richter <robert.richter@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/s390/oprofile/init.c