eCryptfs: Fix oops when printing debug info in extent crypto functions
commit1924fe5874a85f2b25ebb38089e11a6a637e8441
authorTyler Hicks <tyhicks@canonical.com>
Tue, 24 Jan 2012 16:02:22 +0000 (24 10:02 -0600)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 3 Feb 2012 17:21:24 +0000 (3 09:21 -0800)
tree58628f29584afe2c07667f2d5f7ec2688755014a
parent963f50802b55b7df757ec9c44ccab130524c4d54
eCryptfs: Fix oops when printing debug info in extent crypto functions

commit 58ded24f0fcb85bddb665baba75892f6ad0f4b8a upstream.

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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ecryptfs/crypto.c