target: Explicitly clear ramdisk_mcp backend pages
authorNicholas A. Bellinger <nab@linux-iscsi.org>
Mon, 16 Jun 2014 20:59:52 +0000 (20:59 +0000)
committerJiri Slaby <jslaby@suse.cz>
Wed, 2 Jul 2014 10:06:32 +0000 (12:06 +0200)
commit186f32e2096c7d9cd9106b8dedd79c596f4c8398
treecbed90609569a5478abc36cf6421f3d599ea8028
parent3942c33e4b6b84653b04314f526907ae74984f87
target: Explicitly clear ramdisk_mcp backend pages

[Note that a different patch to address the same issue went in during
v3.15-rc1 (commit 4442dc8a), but includes a bunch of other changes that
don't strictly apply to fixing the bug]

This patch changes rd_allocate_sgl_table() to explicitly clear
ramdisk_mcp backend memory pages by passing __GFP_ZERO into
alloc_pages().

This addresses a potential security issue where reading from a
ramdisk_mcp could return sensitive information, and follows what
>= v3.15 does to explicitly clear ramdisk_mcp memory at backend
device initialization time.

Reported-by: Jorge Daniel Sequeira Matias <jdsm@tecnico.ulisboa.pt>
Cc: Jorge Daniel Sequeira Matias <jdsm@tecnico.ulisboa.pt>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
drivers/target/target_core_rd.c