netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	Netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-wireless
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-BGArkANP9klv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
	Alexey Dobriyan
	<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] wireless extensions: play with netns
Date: Wed, 17 Jun 2009 16:54:12 -0700	[thread overview]
Message-ID: <m17hzato0r.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1245282099.31588.69.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org> (Johannes Berg's message of "Thu\, 18 Jun 2009 01\:41\:38 +0200")

Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> writes:

> On Wed, 2009-06-17 at 16:24 -0700, Eric W. Biederman wrote:
>
>> > So it looks like I can also use rcu_read_lock(), but there's no
>> > for_each_net_rcu(), should there be?
>> 
>> I'm not using rcu safe list manipulation.  What makes it look like
>> rcu_read_lock() is safe?
>
> Indeed. I was looking at rcu_barrier() only. How about the patch below?
>
> johannes
>
> Subject: net: make namespace iteration possible under RCU
>
> We already call rcu_barrier(), so all we need to take
> care of is using proper RCU list add/del primitives.

This of course gives you a network namespace that can be found by for_each_net rcu
while the per net exit functions are running.  I think that opens up to races
that I don't want to think about.

I still haven't tracked down how I am occasionally getting time wait sockets
with an invalid network namespace.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-06-17 23:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 18:24 [PATCH] wireless extensions: play with netns Johannes Berg
     [not found] ` <1245263058.31588.38.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-17 20:46   ` Eric W. Biederman
2009-06-17 20:50     ` Johannes Berg
     [not found]     ` <m1y6rqwpur.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-06-17 21:40       ` [PATCH v2] wireless extensions: make netns aware Johannes Berg
2009-06-17 22:14       ` [PATCH] wireless extensions: play with netns Johannes Berg
     [not found]         ` <1245276899.31588.57.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-17 23:24           ` Eric W. Biederman
     [not found]             ` <m1r5xitpdh.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-06-17 23:41               ` Johannes Berg
2009-06-17 23:45                 ` Johannes Berg
     [not found]                   ` <1245282315.31588.71.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-18  0:27                     ` Eric W. Biederman
2009-06-18  0:35                       ` Johannes Berg
     [not found]                 ` <1245282099.31588.69.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-17 23:54                   ` Eric W. Biederman [this message]
     [not found]                     ` <m17hzato0r.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-06-18  0:02                       ` Johannes Berg
     [not found]                         ` <1245283327.31588.74.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-18  0:30                           ` Eric W. Biederman
     [not found]                             ` <m1my86qt73.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-06-18  0:39                               ` Johannes Berg
2009-06-18  1:12                                 ` Eric W. Biederman

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=m17hzato0r.fsf@fess.ebiederm.org \
    --to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
    --cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ebiederm-BGArkANP9klv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).