From: David Miller <davem@davemloft.net>
To: Thomas.Goff@boeing.com
Cc: adobriyan@gmail.com, netdev@vger.kernel.org, adobriyan@openvz.org
Subject: Re: [PATCH] netlink: use the appropriate namespace pid
Date: Fri, 26 Mar 2010 20:15:06 -0700 (PDT) [thread overview]
Message-ID: <20100326.201506.184725289.davem@davemloft.net> (raw)
In-Reply-To: <6AFD35BEDB60334C9A31FD694E13EF0D226771E62E@XCH-NW-18V.nw.nos.boeing.com>
From: "Goff, Thomas" <Thomas.Goff@boeing.com>
Date: Wed, 24 Mar 2010 07:18:12 -0700
> On Wed March 24, 2010 12:59 AM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
>> ACK tgid patch, should have sent it myself long ago.
>
> Thanks for reviewing this.
>
> David is correct that pid is arbitrary here anyway so it really
> shouldn't matter. The patch just lets applications that make an
> incorrect assumption that happens to usually be right for the
> initial namespace work similarly in other namespaces. So
> including the patch seems more of a policy question.
I ended up applying this to net-next-2.6, it's not critical
so it's not net-2.6 material, but it's harmless so we can
still queue it up for the next merge window.
next prev parent reply other threads:[~2010-03-27 3:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 1:38 [PATCH] netlink: use the appropriate namespace pid Tom Goff
2010-03-22 4:30 ` David Miller
2010-03-24 7:58 ` Alexey Dobriyan
2010-03-24 8:19 ` Alexey Dobriyan
2010-03-27 3:14 ` David Miller
2010-03-31 2:42 ` Goff, Thomas
2010-03-31 2:43 ` [PATCH] net_sched: minor netns related cleanup Tom Goff
2010-03-31 2:45 ` David Miller
2010-04-02 1:43 ` David Miller
2010-03-24 14:18 ` [PATCH] netlink: use the appropriate namespace pid Goff, Thomas
2010-03-27 3:15 ` David Miller [this message]
2010-03-23 3:25 ` David Miller
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=20100326.201506.184725289.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Thomas.Goff@boeing.com \
--cc=adobriyan@gmail.com \
--cc=adobriyan@openvz.org \
--cc=netdev@vger.kernel.org \
/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).