All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: avagin@openvz.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, ebiederm@xmission.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH 1/2] ns: Allow ns_entries to have custom symlink content
Date: Mon, 16 Jan 2017 11:18:28 +0300	[thread overview]
Message-ID: <20170116081828.GP28957@uranus.lan> (raw)
In-Reply-To: <148440326011.30622.12833059348082223242.stgit@localhost.localdomain>

On Sat, Jan 14, 2017 at 05:14:48PM +0300, Kirill Tkhai wrote:
> Make possible to have link content prefix yyy
> different from the link name xxx:
> 
> $ readlink /proc/[pid]/ns/xxx
> yyy:[4026531838]
> 
> This will be used in next patch.
> 
> Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>

I don't like much @real_ns_name variable naming, but it's
just personal opinion. The rest looks good to me (for
both patches). If only I didn't miss something obvious.

Reviewed-by: Cyrill Gorcunov <gorcunov@openvz.org>

      parent reply	other threads:[~2017-01-16  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14 14:14 [PATCH 1/2] ns: Allow ns_entries to have custom symlink content Kirill Tkhai
2017-01-14 14:15 ` [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace Kirill Tkhai
2017-01-17 20:00   ` Andrei Vagin
2017-01-17 20:00     ` Andrei Vagin
2017-01-23 21:49   ` Alban Crequy
2017-01-23 21:49     ` Alban Crequy
2017-01-24  8:35     ` Kirill Tkhai
2017-01-24  8:35       ` Kirill Tkhai
2017-01-30 15:10   ` Kirill Tkhai
2017-01-16  8:18 ` Cyrill Gorcunov [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=20170116081828.GP28957@uranus.lan \
    --to=gorcunov@gmail.com \
    --cc=avagin@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.