From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] slub: make sysfs file removal asynchronous
Date: Wed, 28 Jun 2017 09:47:13 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1706280945460.10525@east.gentwo.org> (raw)
In-Reply-To: <20170620224814.GK21326@htj.duckdns.org>
On Tue, 20 Jun 2017, Tejun Heo wrote:
> And we have to weight that against the possibility of breakage from
> the backport, however low it may be, right? I'm not strongly
> convinced either way on this one and AFAICS the slub sysfs files there
> are mostly for debugging, so we'd be risking breakage in a way more
> common path (kmem_cache destruction) to avoid unlikely deadlock with a
> debug facility. I think -stable backports should be conservative and
> justified as breaking things through -stable undermines the whole
> thing.
The sysfs files are mainly used for reporting (the "slabinfo" tool
accesses these files f.e.)
But given the high rate of breakage of sysfs related patches: Lets just
skip stable for now.
prev parent reply other threads:[~2017-06-28 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 12:55 [LOCKDEP BUG] from slub: separate out sysfs_slab_release() from sysfs_slab_remove() Steven Rostedt
2017-06-19 20:35 ` Tejun Heo
2017-06-19 21:27 ` Steven Rostedt
2017-06-20 20:45 ` [PATCH] slub: make sysfs file removal asynchronous Tejun Heo
2017-06-20 21:58 ` Andrew Morton
2017-06-20 22:00 ` Tejun Heo
2017-06-20 22:22 ` Steven Rostedt
2017-06-20 22:48 ` Tejun Heo
2017-06-28 14:47 ` Christoph Lameter [this message]
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=alpine.DEB.2.20.1706280945460.10525@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdavydov.dev@gmail.com \
/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 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).