eCryptfs: Fix oops when printing debug info in extent crypto functions
authorTyler Hicks <tyhicks@canonical.com>
Tue, 24 Jan 2012 16:02:22 +0000 (10:02 -0600)
committerTyler Hicks <tyhicks@canonical.com>
Wed, 25 Jan 2012 20:43:42 +0000 (14:43 -0600)
commit58ded24f0fcb85bddb665baba75892f6ad0f4b8a
tree40190011c2c728cfcfae82e105800958ddc92399
parentf2cb933501ebc066bf3c4b1836fd8428f8fe9863
eCryptfs: Fix oops when printing debug info in extent crypto functions

If pages passed to the eCryptfs extent-based crypto functions are not
mapped and the module parameter ecryptfs_verbosity=1 was specified at
loading time, a NULL pointer dereference will occur.

Note that this wouldn't happen on a production system, as you wouldn't
pass ecryptfs_verbosity=1 on a production system. It leaks private
information to the system logs and is for debugging only.

The debugging info printed in these messages is no longer very useful
and rather than doing a kmap() in these debugging paths, it will be
better to simply remove the debugging paths completely.

https://launchpad.net/bugs/913651

Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Reported-by: Daniel DeFreez
Cc: <stable@vger.kernel.org>
fs/ecryptfs/crypto.c