From: David Rientjes <email@example.com>
To: Vlastimil Babka <firstname.lastname@example.org>
Cc: Kees Cook <email@example.com>, Jann Horn <firstname.lastname@example.org>,
Christoph Lameter <email@example.com>,
Pekka Enberg <firstname.lastname@example.org>,
Joonsoo Kim <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
kernel list <email@example.com>,
Matthew Garrett <firstname.lastname@example.org>,
Vijayanand Jitta <email@example.com>
Subject: Re: SLUB: sysfs lets root force slab order below required minimum, causing memory corruption
Date: Wed, 4 Mar 2020 12:39:52 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.firstname.lastname@example.org> (raw)
On Wed, 4 Mar 2020, Vlastimil Babka wrote:
> > Seems reasonable!
> > For the race concerns, should this logic just make sure the resulting
> > order can never shrink? Or does it need much stronger atomicity?
> If order grows, I think we also need to recalculate the random sequence for
> freelist randomization . I expect that would be rather problematic with
> parallel allocations/freeing going on.
> As was also noted, the any_slab_objects(s) checks are racy - might return false
> and immediately some other CPU can allocate some.
> I wonder if this race window could be fixed at all without introducing extra
> locking in the fast path? Which means it's probably not worth the trouble of
> having these runtime knobs. How about making the files read-only (if not remove
> completely). Vijayanand described a use case in , shouldn't it be possible to
> implement that scenario (all caches have debugging enabled except zram cache)
> with kernel parameters only?
I'm not sure how dependent the CONFIG_SLUB_DEBUG users are on being able
to modify these are runtime (they've been around for 12+ years) but I
agree that it seems particularly dangerous.
I think they can be fixed by freezing allocations and frees for the
particular kmem_cache on all cpus which would add the additional
conditional in the fastpath and that's going to be required in the very
small minority of cases where an admin actually wants to change these.
The slub_debug kernel command line options are already pretty
comprehensive as described by Documentation/vm/slub.rst. I *think* these
tunables were primarily introduced for kernel debugging and not general
purpose, perhaps with the exception of "order".
So I think we may be able to fix "order" with a combination of my patch as
well as a fix to the freelist randomization and that the others should
likely be made read only.
next prev parent reply other threads:[~2020-03-04 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 0:23 SLUB: sysfs lets root force slab order below required minimum, causing memory corruption Jann Horn
2020-03-04 1:26 ` David Rientjes
2020-03-04 2:22 ` Kees Cook
2020-03-04 17:26 ` Vlastimil Babka
2020-03-04 20:39 ` David Rientjes [this message]
2020-03-08 19:34 ` Christopher Lameter
2020-03-04 14:57 ` Pekka Enberg
2020-03-04 13:17 ` Vlastimil Babka
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).