ecryptfs: fix kernel panic with null dev_name
authorJeffrey Mitchell <jeffrey.mitchell@starlab.io>
Fri, 26 Feb 2021 21:00:23 +0000 (15:00 -0600)
committerTyler Hicks <code@tyhicks.com>
Mon, 19 Apr 2021 05:50:32 +0000 (05:50 +0000)
commit9046625511ad8dfbc8c6c2de16b3532c43d68d48
treed2b00bbc0f0d0c975a245ba0c093823c4da8028c
parent7f06ecd3afb0f976a324d5d8505242c67e4b4719
ecryptfs: fix kernel panic with null dev_name

When mounting eCryptfs, a null "dev_name" argument to ecryptfs_mount()
causes a kernel panic if the parsed options are valid. The easiest way to
reproduce this is to call mount() from userspace with an existing
eCryptfs mount's options and a "source" argument of 0.

Error out if "dev_name" is null in ecryptfs_mount()

Fixes: 237fead61998 ("[PATCH] ecryptfs: fs/Makefile and fs/Kconfig")
Cc: stable@vger.kernel.org
Signed-off-by: Jeffrey Mitchell <jeffrey.mitchell@starlab.io>
Signed-off-by: Tyler Hicks <code@tyhicks.com>
fs/ecryptfs/main.c