netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: john.r.fastabend@intel.com
Cc: mark.d.rustad@intel.com, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: That's pretty much it for 3.5.0
Date: Tue, 17 Jul 2012 14:02:41 -0700 (PDT)	[thread overview]
Message-ID: <20120717.140241.1599386555723262095.davem@davemloft.net> (raw)
In-Reply-To: <5005D008.6060103@intel.com>

From: John Fastabend <john.r.fastabend@intel.com>
Date: Tue, 17 Jul 2012 13:50:16 -0700

> On 7/17/2012 12:24 PM, David Miller wrote:
>> From: John Fastabend <john.r.fastabend@intel.com>
>> Date: Tue, 17 Jul 2012 12:09:53 -0700
>>
>>> although we don't have an early_init hook for netprio_cgroup so this
>>> is probably not correct.
>>
>> The dependency is actually on net_dev_init (a subsys_initcall) rather
>> than a pure_initcall.
>>
>> net_dev_init is what registers the netdev_net_ops, which in turn
>> initializes the netdev list in namespaces such as &init_net
>>
> 
> Ah right thanks sorry for the thrash. I guess we need to check if the
> netdev list in the init_net namespace is initialized.

It's a hack, but we could export and then test dev_boot_phase == 0,
and if that test is true then skip the init_net device walk in the
cgroup code.

But I don't like that very much.

The things this code cares about can't even be an issue until
net_dev_init() runs.

There is a comment warning not to do this in linux/init.h, but we
could change the module_init() in netprio_cgroup.c to some level which
runs after subsys_inticall().  When built as a module, linux/init.h
will translate this into module_init() which is basically the behavior
we want.

  reply	other threads:[~2012-07-17 21:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 16:01 That's pretty much it for 3.5.0 David Miller
2012-07-17 17:41 ` Rustad, Mark D
2012-07-17 18:48   ` Rustad, Mark D
2012-07-17 19:00     ` John Fastabend
2012-07-17 19:09       ` John Fastabend
     [not found]         ` <5005B881.8010505-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-07-17 19:17           ` John Fastabend
2012-07-17 19:26             ` John Fastabend
2012-07-17 19:24         ` David Miller
2012-07-17 20:50           ` John Fastabend
2012-07-17 21:02             ` David Miller [this message]
2012-07-17 22:13               ` John Fastabend
2012-07-17 22:18                 ` David Miller
     [not found]                   ` <20120717.151832.1306978935355646723.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-07-17 23:27                     ` John Fastabend
2012-07-18 13:04                       ` Neil Horman
2012-07-18 17:36                         ` Rustad, Mark D
2012-07-18 17:55                           ` Eric Dumazet
2012-07-18 18:31                             ` Rustad, Mark D
     [not found]                               ` <FEB6B45E-1CCF-4CBC-AEB7-21D2088E175C-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2012-07-18 18:33                                 ` 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=20120717.140241.1599386555723262095.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=john.r.fastabend@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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).