From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: michele@acksyn.org, netdev@vger.kernel.org,
yoshfuji@linux-ipv6.org, sasha.levin@oracle.com
Subject: Re: [PATCH] ipv6: fix null pointer dereference in __ip6addrlbl_add
Date: Wed, 04 Sep 2013 14:58:16 -0400 (EDT) [thread overview]
Message-ID: <20130904.145816.1990856496857762166.davem@davemloft.net> (raw)
In-Reply-To: <20130904185145.GC13136@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 4 Sep 2013 20:51:45 +0200
> Sorry I forgot to mention that this patch is also applicable to solve
> this issue in the longterm 3.10 kernel. Maybe this should go to stable?
I did queue it up for -stable already.
prev parent reply other threads:[~2013-09-04 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 21:31 3.11rc7 net/ipv6 addrlabel OOPS Michele Baldessari
2013-09-03 0:13 ` [PATCH] ipv6: fix null pointer dereference in __ip6addrlbl_add Hannes Frederic Sowa
2013-09-03 8:04 ` Michele Baldessari
2013-09-04 18:13 ` David Miller
2013-09-04 18:51 ` Hannes Frederic Sowa
2013-09-04 18:58 ` 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=20130904.145816.1990856496857762166.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=michele@acksyn.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=yoshfuji@linux-ipv6.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).