summaryrefslogtreecommitdiffstats
path: root/fs/exofs/sys.c
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2014-05-19 15:52:10 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-05-20 10:15:53 +0900
commitf5c16f29bf5e57ba4051fc7785ba7f035f798c71 (patch)
treec7dadc302a01d7837ffb437a0d46618111aaf3a9 /fs/exofs/sys.c
parent555724a831b4a146e7bdf16ecc989cda032b076d (diff)
downloadop-kernel-dev-f5c16f29bf5e57ba4051fc7785ba7f035f798c71.zip
op-kernel-dev-f5c16f29bf5e57ba4051fc7785ba7f035f798c71.tar.gz
sysfs: make sure read buffer is zeroed
13c589d5b0ac ("sysfs: use seq_file when reading regular files") switched sysfs from custom read implementation to seq_file to enable later transition to kernfs. After the change, the buffer passed to ->show() is acquired through seq_get_buf(); unfortunately, this introduces a subtle behavior change. Before the commit, the buffer passed to ->show() was always zero as it was allocated using get_zeroed_page(). Because seq_file doesn't clear buffers on allocation and neither does seq_get_buf(), after the commit, depending on the behavior of ->show(), we may end up exposing uninitialized data to userland thus possibly altering userland visible behavior and leaking information. Fix it by explicitly clearing the buffer. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Ron <ron@debian.org> Fixes: 13c589d5b0ac ("sysfs: use seq_file when reading regular files") Cc: stable <stable@vger.kernel.org> # 3.13+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/exofs/sys.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud