linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Zefan Li <lizefan@huawei.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, Andrey Vagin <avagin@openvz.org>
Subject: Re: [heads-up] buggered refcounting logics in cgroup1_mount()
Date: Tue, 15 Jan 2019 07:26:27 -0800	[thread overview]
Message-ID: <20190115152627.GB168429@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190112215215.GV2217@ZenIV.linux.org.uk>

Hello, Al.

On Sat, Jan 12, 2019 at 09:52:15PM +0000, Al Viro wrote:
> > See vfs.git #fixes (the last two commits in there).  It seems to
> > work here, but I don't have the CRIU regression tests, etc., so
> > I would really appreciate if that thing got a real beating.
> 
> BTW, while kernfs_pin_sb() and struct kernfs_root ->supers definitely
> ought to die, there's something else that might be killable with that
> approach.  percpu_ref_reinit() has no users left after that, and,
> as David Howells has observed, PERCPU_REF_INIT_DEAD is also unused.
> 
> Do we want to keep these two?

Sorry about the delay.

* The patches look good to me.  That said, of the two patches, I think
  it'd be probably better to send only the first one to -stable.  As
  there haven't been any bug reports against the mount behavior for
  some years now, I don't think there's a need to backport the bigger
  change.  Any change carries some risk after all.

* Please feel free to remove percpu_ref_reinit() and unused parts.
  It's easy enough to add it back later if necessary.

* How do you wanna route the patches?

Thanks.

-- 
tejun

  reply	other threads:[~2019-01-15 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  7:23 [heads-up] buggered refcounting logics in cgroup1_mount() Al Viro
2019-01-11 20:54 ` Tejun Heo
2019-01-12  5:38   ` Al Viro
2019-01-12 21:52     ` Al Viro
2019-01-15 15:26       ` Tejun Heo [this message]
2019-01-14  1:31   ` Zefan Li

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=20190115152627.GB168429@devbig004.ftw2.facebook.com \
    --to=tj@kernel.org \
    --cc=avagin@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).