From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: Cong Wang <xiyou.wangcong@gmail•com>,
Dan Carpenter <dan.carpenter@oracle•com>
Cc: kernel-janitors@vger•kernel.org,
Linux Kernel Network Developers <netdev@vger•kernel.org>
Subject: Re: netns: use a spin_lock to protect nsid management
Date: Wed, 13 May 2015 13:58:25 +0200 [thread overview]
Message-ID: <55533C61.2030206@6wind.com> (raw)
In-Reply-To: <CAM_iQpUSgpeL_Dy+U+KrBd=h3bhm03vASupdO-9dSs+CKYjNeg@mail.gmail.com>
Le 12/05/2015 21:16, Cong Wang a écrit :
[snip]
> Also why do we have to disable IRQ when holding the spinlock?
> IOW, which case takes the spin lock in IRQ context?
peernet2id() is called by do_one_broadcast() (net/netlink/af_netlink.c). So
every callers of netlink_broadcast[_filtered]()/nlmsg_unicast()
/nlmsg_multicast() may needs this lock.
next prev parent reply other threads:[~2015-05-13 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150512175227.GA19020@mwanda>
2015-05-12 19:16 ` netns: use a spin_lock to protect nsid management Cong Wang
2015-05-13 11:58 ` Nicolas Dichtel [this message]
2015-05-13 11:37 ` Nicolas Dichtel
2015-05-13 11:43 ` [PATCH net-next] netns: fix unbalanced spin_lock on error Nicolas Dichtel
2015-05-15 2:36 ` 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=55533C61.2030206@6wind.com \
--to=nicolas.dichtel@6wind$(echo .)com \
--cc=dan.carpenter@oracle$(echo .)com \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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