From: Al Viro <viro@ZenIV.linux.org.uk>
To: Tej Parkash <bewith.tej@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PANIC with linux-next-2.6.26-next-20080718
Date: Mon, 21 Jul 2008 14:20:27 +0100 [thread overview]
Message-ID: <20080721132027.GD28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <f1c9d250807210348w58aa132che5543cb30a33ee60@mail.gmail.com>
On Mon, Jul 21, 2008 at 04:18:35PM +0530, Tej Parkash wrote:
> while testing linux-next with commit
> "commit 43a2c1df777e18dfb0ba48d03b4f8b8ff80f1b57"
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri Jul 18 19:27:47 2008 +1000
>
> machine hang with the following panic. config/cpuinfo/lspci are attached.
> trying git-bisect.
Apply the patch below or try the current linux-next where vfs-next is
rebased on top of net-next with that sucker folded in.
diff --git a/net/sysctl_net.c b/net/sysctl_net.c
index b91a5de..2240a9e 100644
--- a/net/sysctl_net.c
+++ b/net/sysctl_net.c
@@ -44,13 +44,6 @@ static struct ctl_table_root net_sysctl_root = {
.lookup = net_ctl_header_lookup,
};
-static LIST_HEAD(net_sysctl_ro_tables);
-static struct list_head *net_ctl_ro_header_lookup(struct ctl_table_root *root,
- struct nsproxy *namespaces)
-{
- return &net_sysctl_ro_tables;
-}
-
static int net_ctl_ro_header_perms(struct ctl_table_root *root,
struct nsproxy *namespaces, struct ctl_table *table)
{
@@ -61,7 +54,6 @@ static int net_ctl_ro_header_perms(struct ctl_table_root *root,
}
static struct ctl_table_root net_sysctl_ro_root = {
- .lookup = net_ctl_ro_header_lookup,
.permissions = net_ctl_ro_header_perms,
};
@@ -89,6 +81,7 @@ static __init int sysctl_init(void)
if (ret)
goto out;
register_sysctl_root(&net_sysctl_root);
+ setup_sysctl_set(&net_sysctl_ro_root.default_set, NULL, NULL);
register_sysctl_root(&net_sysctl_ro_root);
out:
return ret;
next prev parent reply other threads:[~2008-07-21 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 10:48 PANIC with linux-next-2.6.26-next-20080718 Tej Parkash
2008-07-21 13:20 ` Al Viro [this message]
2008-07-22 11:08 ` Tej
2008-07-22 11:25 ` Tej
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=20080721132027.GD28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bewith.tej@gmail.com \
--cc=linux-kernel@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