All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Goff <thomas.goff@boeing.com>
To: netdev@vger.kernel.org
Subject: [PATCH] netlink: use the appropriate namespace pid
Date: Fri, 19 Mar 2010 18:38:50 -0700	[thread overview]
Message-ID: <20100320013850.GA13239@boeing.com> (raw)

This was included in OpenVZ kernels but wasn't integrated upstream.
>From git://git.openvz.org/pub/linux-2.6.24-openvz:

	commit 5c69402f18adf7276352e051ece2cf31feefab02
	Author: Alexey Dobriyan <adobriyan@openvz.org>
	Date:   Mon Dec 24 14:37:45 2007 +0300

	    netlink: fixup ->tgid to work in multiple PID namespaces

Signed-off-by: Tom Goff <thomas.goff@boeing.com>
---
 net/netlink/af_netlink.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
index 320d042..b5ac0cd 100644
--- a/net/netlink/af_netlink.c
+++ b/net/netlink/af_netlink.c
@@ -545,7 +545,7 @@ static int netlink_autobind(struct socket *sock)
 	struct hlist_head *head;
 	struct sock *osk;
 	struct hlist_node *node;
-	s32 pid = current->tgid;
+	s32 pid = task_tgid_vnr(current);
 	int err;
 	static s32 rover = -4097;
 
-- 
1.6.3.3


             reply	other threads:[~2010-03-20  2:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  1:38 Tom Goff [this message]
2010-03-22  4:30 ` [PATCH] netlink: use the appropriate namespace pid 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
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=20100320013850.GA13239@boeing.com \
    --to=thomas.goff@boeing.com \
    --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 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.