From: Stephen Hemminger <shemminger@vyatta.com>
To: Lucian Adrian Grijincu <lucian.grijincu@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: net-next: warnings from sysctl_net_exit
Date: Sun, 27 Feb 2011 16:08:52 -0800 [thread overview]
Message-ID: <20110227160852.4f748c1f@nehalam> (raw)
In-Reply-To: <AANLkTi=mhj3Ftq8hFPPzZYJvp8mgOeV89oX_vHZVxwzY@mail.gmail.com>
On Mon, 28 Feb 2011 00:37:09 +0200
Lucian Adrian Grijincu <lucian.grijincu@gmail.com> wrote:
> Stephen Hemminger <shemminger <at> vyatta.com> writes:
> > [26207.669740] [<ffffffff814154ad>] ? sysctl_net_exit+0x2a/0x2c
> > [26207.669742] [<ffffffff8136144e>] ? ops_exit_list+0x2a/0x5b
> > [26207.669745] [<ffffffff813618f0>] ? cleanup_net+0xfa/0x19a
>
>
> David: it looks like someone registered a /proc/sys table with
> register_net_sysctl_table but forgot to remove it (or someone wrote
> something in the 'struct net*' and buffer overflowed into
> &net->sysctls.list).
>
> Stephen, can you post a `ls -R /proc/sys/net/` from before the dmesg
> message appeared?
>
> The check is triggered at network namespace deletion, so a moment
> before deleting the netns should be fine.
Although the kernel was compiled with netns, I never use net namespaces.
next prev parent reply other threads:[~2011-02-28 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 22:37 net-next: warnings from sysctl_net_exit Lucian Adrian Grijincu
2011-02-27 23:34 ` David Miller
2011-02-28 0:49 ` Lucian Adrian Grijincu
2011-02-28 0:08 ` Stephen Hemminger [this message]
2011-02-28 1:11 ` Lucian Adrian Grijincu
2011-02-28 22:02 ` Stephen Hemminger
2011-03-02 7:09 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2011-02-27 0:56 Stephen Hemminger
2011-02-27 6:23 ` David Miller
2011-02-27 18:45 ` Stephen Hemminger
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=20110227160852.4f748c1f@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=lucian.grijincu@gmail.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.