From: David Miller <davem@davemloft.net>
To: kyle@infradead.org
Cc: cebbert@redhat.com, netdev@vger.kernel.org
Subject: Re: oops / null deref in __inet6_check_established(), kernel 2.6.29-rc6
Date: Sun, 01 Mar 2009 21:28:57 -0800 (PST) [thread overview]
Message-ID: <20090301.212857.264627839.davem@davemloft.net> (raw)
In-Reply-To: <20090302050919.GJ28503@bombadil.infradead.org>
From: Kyle McMartin <kyle@infradead.org>
Date: Mon, 2 Mar 2009 00:09:19 -0500
> On Fri, Feb 27, 2009 at 10:16:18PM -0500, Kyle McMartin wrote:
> > This only seems to show up when CONFIG_NET_NS is enabled. (Reproduced on
> > git HEAD with that option on, doesn't occur with the option off.)
> >
> > I will confess complete ignorance to the network stack, but this patch
> > fixes things... ipv4 seems to have the same namespace support, but
> > increments the sock_net, not the twsk_net.
> >
> > I'll probably put this patch into Fedora, if only to prevent this from
> > being used as a local DoS by an unprivileged user.
> >
> > Signed-off-by: Kyle McMartin <kyle@redhat.com>
> >
>
> Any thoughts? This is a pretty serious issue... Granted we should
> probably just turn CONFIG_NET_NS off entirely, since it's
> underdocumented and should be explicitly labelled as experimental
> instead of just depending on it...
It's in my queue, I just haven't gotten to it yet.
Serious issue or not you have to be patient.
next prev parent reply other threads:[~2009-03-02 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 23:21 oops / null deref in __inet6_check_established(), kernel 2.6.29-rc6 Chuck Ebbert
2009-02-24 23:27 ` David Miller
2009-02-24 23:35 ` Chuck Ebbert
2009-02-28 3:16 ` Kyle McMartin
2009-03-02 5:09 ` Kyle McMartin
2009-03-02 5:28 ` David Miller [this message]
2009-03-02 5:33 ` David Miller
2009-03-02 17:18 ` Kyle McMartin
2009-03-03 22:21 ` 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=20090301.212857.264627839.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cebbert@redhat.com \
--cc=kyle@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox