From: Djalal Harouni <djalal@endocode.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: "Iago López Galeiras" <iago@endocode.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"Kees Cook" <keescook@chromium.org>,
"Pavel Emelyanov" <xemul@parallels.com>,
"Serge Hallyn" <serge.hallyn@canonical.com>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
linux-api@vger.kernel.org,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Alban Crequy" <alban@endocode.com>
Subject: Re: [PATCH] fs, proc: introduce CONFIG_PROC_CHILDREN
Date: Tue, 26 May 2015 16:07:19 +0100 [thread overview]
Message-ID: <20150526150719.GA8165@dztty> (raw)
In-Reply-To: <20150522153705.GI16716@uranus>
On Fri, May 22, 2015 at 06:37:05PM +0300, Cyrill Gorcunov wrote:
> On Fri, May 22, 2015 at 02:47:39PM +0200, Iago López Galeiras wrote:
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -1145,6 +1145,7 @@ endif # CGROUPS
> >
> > config CHECKPOINT_RESTORE
> > bool "Checkpoint/restore support" if EXPERT
> > + depends on PROC_CHILDREN
> > default n
> > help
> > Enables additional kernel features in a sake of checkpoint/restore.
>
> Maybe better select PROC_CHILDREN here? Also I must admit I don't understand
> why similar patch from Andy has not been merged earlier? Andy, there was
> some problem I forgot about?
From the linked thread, it seems that it was just lost... The discussion
ended up about task/<tid> and /proc/<pid>... That patch should have been
applied.
BTW this patch adds the CONFIG guard that was requested by Andrew. There
is a v3 coming to make it "select" as suggested.
Thanks!
--
Djalal Harouni
http://opendz.org
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-26 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 10:30 [PATCH] [RFC] fs, proc: don't guard /proc/<pid>/task/<tid>/children on CONFIG_CHECKPOINT_RESTORE Alban Crequy
2015-05-21 20:57 ` Andrew Morton
2015-05-22 12:47 ` [PATCH] fs, proc: introduce CONFIG_PROC_CHILDREN Iago López Galeiras
[not found] ` <1432298859-2059-1-git-send-email-iago-973cpzSjLbNWk0Htik3J/w@public.gmane.org>
2015-05-22 15:37 ` Cyrill Gorcunov
2015-05-26 15:07 ` Djalal Harouni [this message]
2015-05-26 15:12 ` [PATCH v3] " Iago López Galeiras
[not found] ` <1432653162-20973-1-git-send-email-iago-973cpzSjLbNWk0Htik3J/w@public.gmane.org>
2015-05-27 7:29 ` Cyrill Gorcunov
[not found] ` <1432204221-1933-1-git-send-email-alban-973cpzSjLbNWk0Htik3J/w@public.gmane.org>
2015-05-21 21:47 ` [PATCH] [RFC] fs, proc: don't guard /proc/<pid>/task/<tid>/children on CONFIG_CHECKPOINT_RESTORE Andy Lutomirski
[not found] ` <CALCETrVbaKnqj7qLBr+ufirPHfdjAYzo6_e362N0muVGnH7HTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-21 22:05 ` Cyrill Gorcunov
2015-05-22 12:49 ` Alban Crequy
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=20150526150719.GA8165@dztty \
--to=djalal@endocode.com \
--cc=akpm@linux-foundation.org \
--cc=alban@endocode.com \
--cc=gorcunov@gmail.com \
--cc=iago@endocode.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=serge.hallyn@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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).