From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: don't use tw net when accounting for recycled tw
Date: Thu, 26 Feb 2009 03:35:54 -0800 (PST) [thread overview]
Message-ID: <20090226.033554.143229118.davem@davemloft.net> (raw)
In-Reply-To: <49A67DAB.9060203@openvz.org>
From: Pavel Emelyanov <xemul@openvz.org>
Date: Thu, 26 Feb 2009 14:31:55 +0300
> We already have a valid net in that place, but this is not just a
> cleanup - the tw pointer can be NULL there sometimes, thus causing
> an oops in NET_NS=y case.
>
> The same place in ipv4 code already works correctly using existing
> net, rather than tw's one.
>
> The bug exists since 2.6.27.
>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Applied and queued up for -stable, thanks!
prev parent reply other threads:[~2009-02-26 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 11:31 [PATCH] ipv6: don't use tw net when accounting for recycled tw Pavel Emelyanov
2009-02-26 11:35 ` David Miller [this message]
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=20090226.033554.143229118.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).