From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Aditya Kali <adityakali@google.com>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: Fix namespace mountpoint path in /proc/mounts
Date: Thu, 21 Nov 2013 22:52:21 +0000 [thread overview]
Message-ID: <20131121225221.GA10445@mail.hallyn.com> (raw)
In-Reply-To: <87r4a974rb.fsf@xmission.com>
Quoting Eric W. Biederman (ebiederm@xmission.com):
> "Serge E. Hallyn" <serge@hallyn.com> writes:
>
> > Aditya, is this something you'd have time to write a patch for?
>
> I have a tested patch that fixes when we call ns_dname. Give me a day
> and I will push out my pending pile of fixes for review.
>
> Eric
Oh, awesome, thanks!
-serge
prev parent reply other threads:[~2013-11-21 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 21:51 [PATCH] proc: Fix namespace mountpoint path in /proc/mounts Aditya Kali
2013-10-29 15:36 ` Serge E. Hallyn
2013-11-08 23:54 ` Eric W. Biederman
2013-11-21 21:50 ` Serge E. Hallyn
2013-11-21 22:46 ` Eric W. Biederman
2013-11-21 22:52 ` Serge E. Hallyn [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=20131121225221.GA10445@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=adityakali@google.com \
--cc=ebiederm@xmission.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 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).