From: Tejun Heo <tj@kernel.org>
To: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>
Cc: Andrei Vagin <avagin@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call
Date: Thu, 12 May 2016 11:02:22 -0400 [thread overview]
Message-ID: <20160512150222.GP4775@htj.duckdns.org> (raw)
In-Reply-To: <20160512052945.GA30046@mail.hallyn.com>
On Thu, May 12, 2016 at 12:29:45AM -0500, Serge E. Hallyn wrote:
> Our caller expects 0 on success, not >0.
>
> This fixes a bug in the patch
>
> cgroup, kernfs: make mountinfo show properly scoped path for cgroup namespaces
>
> where /sys does not show up in mountinfo, breaking criu.
>
> Thanks for catching this, Andrei.
>
> Reported-by: Andrei Vagin <avagin@gmail.com>
> Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
Applied to cgroup/for-4.6-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2016-05-12 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 0:10 cgroup, kernfs: make mountinfo show properly scoped path for cgroup namespaces Andrei Vagin
2016-05-12 5:29 ` [PATCH] kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call Serge E. Hallyn
2016-05-12 15:02 ` Tejun Heo [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=20160512150222.GP4775@htj.duckdns.org \
--to=tj@kernel.org \
--cc=avagin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@ubuntu.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