From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: Tree for November 7
Date: Sat, 8 Nov 2008 12:57:44 +0100 [thread overview]
Message-ID: <200811081257.45184.bzolnier@gmail.com> (raw)
In-Reply-To: <20081107205457.f64dea59.sfr@canb.auug.org.au>
Hi,
On Friday 07 November 2008, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20081106:
The following patch fixes the panic on loopback device registration
(patch is an interdiff between old and new version of "net: Guaranetee
the proper ordering of the loopback device." fix from Eric).
[ I'm sure this will get fixed in -net tree (if not fixed already)
but at the moment it is needed for linux-next. ]
---
net/core/dev.c | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
Index: b/net/core/dev.c
===================================================================
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -4913,21 +4913,6 @@ static int __init net_dev_init(void)
if (register_pernet_subsys(&netdev_net_ops))
goto out;
- /* The loopback device is special if any other network devices
- * is present in a network namespace the loopback device must
- * be present. Since we now dynamically allocate and free the
- * loopback device ensure this invariant is maintained by
- * keeping the loopback device as the first device on the
- * list of network devices. Ensuring the loopback devices
- * is the first device that appears and the last network device
- * that disappears.
- */
- if (register_pernet_device(&loopback_net_ops))
- goto out;
-
- if (register_pernet_device(&default_device_ops))
- goto out;
-
/*
* Initialise the packet receive queues.
*/
@@ -4944,10 +4929,25 @@ static int __init net_dev_init(void)
queue->backlog.weight = weight_p;
}
- netdev_dma_register();
-
dev_boot_phase = 0;
+ /* The loopback device is special if any other network devices
+ * is present in a network namespace the loopback device must
+ * be present. Since we now dynamically allocate and free the
+ * loopback device ensure this invariant is maintained by
+ * keeping the loopback device as the first device on the
+ * list of network devices. Ensuring the loopback devices
+ * is the first device that appears and the last network device
+ * that disappears.
+ */
+ if (register_pernet_device(&loopback_net_ops))
+ goto out;
+
+ if (register_pernet_device(&default_device_ops))
+ goto out;
+
+ netdev_dma_register();
+
open_softirq(NET_TX_SOFTIRQ, net_tx_action);
open_softirq(NET_RX_SOFTIRQ, net_rx_action);
next prev parent reply other threads:[~2008-11-08 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 9:54 linux-next: Tree for November 7 Stephen Rothwell
2008-11-07 22:30 ` next-20081107: ia64 vs kvm Alexey Dobriyan
2008-11-08 7:57 ` Zhang, Xiantao
2008-11-09 10:00 ` Avi Kivity
2008-11-07 23:04 ` linux-next: Tree for November 7 Alexey Dobriyan
2008-11-08 11:57 ` Bartlomiej Zolnierkiewicz [this message]
2008-11-08 18:43 ` Alexey Dobriyan
2008-11-08 19:13 ` Bartlomiej Zolnierkiewicz
2008-11-10 6:45 ` KAMEZAWA Hiroyuki
2008-11-10 8:12 ` KAMEZAWA Hiroyuki
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=200811081257.45184.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).