summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorJeff Layton <jlayton@poochiereds.net>2015-03-31 16:03:28 (GMT)
committerJ. Bruce Fields <bfields@redhat.com>2015-03-31 18:15:08 (GMT)
commitf9c72d10d6fbf949558cd088389a42213ed7b12d (patch)
treec40dbd4ff8c6d1f94f3406597eeca74208ba4668 /drivers
parentf3f03330dee0526d82f2a0fd1a79d207ed1ac439 (diff)
downloadlinux-f9c72d10d6fbf949558cd088389a42213ed7b12d.tar.xz
sunrpc: make debugfs file creation failure non-fatal
We currently have a problem that SELinux policy is being enforced when creating debugfs files. If a debugfs file is created as a side effect of doing some syscall, then that creation can fail if the SELinux policy for that process prevents it. This seems wrong. We don't do that for files under /proc, for instance, so Bruce has proposed a patch to fix that. While discussing that patch however, Greg K.H. stated: "No kernel code should care / fail if a debugfs function fails, so please fix up the sunrpc code first." This patch converts all of the sunrpc debugfs setup code to be void return functins, and the callers to not look for errors from those functions. This should allow rpc_clnt and rpc_xprt creation to work, even if the kernel fails to create debugfs files for some reason. Symptoms were failing krb5 mounts on systems using gss-proxy and selinux. Fixes: 388f0c776781 "sunrpc: add a debugfs rpc_xprt directory..." Cc: stable@vger.kernel.org Signed-off-by: Jeff Layton <jeff.layton@primarydata.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions