From: Al Viro <viro@zeniv.linux.org.uk>
To: Thibaut Sautereau <thibaut@sautereau.fr>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Christian Brauner <christian@brauner.io>,
cgroups@vger.kernel.org
Subject: Re: NULL pointer deref in put_fs_context with unprivileged LXC
Date: Wed, 6 Nov 2019 07:24:07 +0000 [thread overview]
Message-ID: <20191106072407.GU26530@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20191105205830.GA871@gandi.net>
On Tue, Nov 05, 2019 at 09:58:30PM +0100, Thibaut Sautereau wrote:
> > > BUG: kernel NULL pointer dereference, address: 0000000000000043
ERR_PTR(something)->d_sb, most likely.
> > > 493 if (fc->root) {
> > > 494 sb = fc->root->d_sb;
> > > 495 dput(fc->root);
> > > 496 fc->root = NULL;
> > > 497 deactivate_super(sb);
> > > 498 }
> fs_context: DEBUG: fc->root = fffffffffffffff3
> fs_context: DEBUG: fc->source = cgroup2
Yup. That'd be ERR_PTR(-13), i.e. ERR_PTR(-EACCES). Most likely
from
nsdentry = kernfs_node_dentry(cgrp->kn, sb);
dput(fc->root);
fc->root = nsdentry;
if (IS_ERR(nsdentry)) {
ret = PTR_ERR(nsdentry);
deactivate_locked_super(sb);
}
in cgroup_do_get_tree(). As a quick test, try to add fc->root = NULL;
next to that deactivate_locked_super(sb); inside the if (IS_ERR(...))
body and see if it helps; it's not the best way to fix it (I'd rather
go for
if (IS_ERR(nsdentry)) {
ret = PTR_ERR(nsdentry);
deactivate_locked_super(sb);
nsdentry = NULL;
}
fc->root = nsdentry;
), but it would serve to verify that this is the source of that crap.
next prev parent reply other threads:[~2019-11-06 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 21:35 NULL pointer deref in put_fs_context with unprivileged LXC Thibaut Sautereau
2019-10-11 14:14 ` Christian Brauner
2019-11-05 20:58 ` Thibaut Sautereau
2019-11-06 7:24 ` Al Viro [this message]
2019-11-06 21:06 ` Thibaut Sautereau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191106072407.GU26530@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=cgroups@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thibaut@sautereau.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.