From: "Luís Henriques" <luis.henriques@canonical.com>
To: David Miller <davem@davemloft.net>
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, 4 Apr 2014 15:45:12 +0100 [thread overview]
Message-ID: <20140404144512.GB2593@hercules> (raw)
In-Reply-To: <20140404.104426.2226769084775433079.davem@davemloft.net>
On Fri, Apr 04, 2014 at 10:44:26AM -0400, David Miller wrote:
> 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.
That was fast! Thanks :)
Cheers,
--
Luís
prev parent reply other threads:[~2014-04-04 14:45 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
2014-04-04 14:45 ` Luís Henriques [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=20140404144512.GB2593@hercules \
--to=luis.henriques@canonical.com \
--cc=chien.yen@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.