From: David Miller <davem@davemloft.net>
To: luis.henriques@canonical.com
Cc: sasha.levin@oracle.com, chien.yen@oracle.com,
rds-devel@oss.oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rds: prevent dereference of a NULL device in rds_iw_laddr_check
Date: Fri, 04 Apr 2014 10:44:26 -0400 (EDT) [thread overview]
Message-ID: <20140404.104426.2226769084775433079.davem@davemloft.net> (raw)
In-Reply-To: <20140404143136.GA2593@hercules>
From: Luís Henriques <luis.henriques@canonical.com>
Date: Fri, 4 Apr 2014 15:31:36 +0100
> Could you please queue this one for stable as well? (Looks like it even
> has CVE-2014-2678 assigned to it.)
Done.
next prev parent reply other threads:[~2014-04-04 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 0:39 [PATCH v2] rds: prevent dereference of a NULL device in rds_iw_laddr_check Sasha Levin
2014-03-31 20:26 ` David Miller
2014-04-04 14:31 ` Luís Henriques
2014-04-04 14:44 ` David Miller [this message]
2014-04-04 14:45 ` Luís Henriques
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=20140404.104426.2226769084775433079.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chien.yen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sasha.levin@oracle.com \
/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).