From: Steffen Klassert <steffen.klassert@secunet.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <dan.carpenter@oracle.com>,
<kbuild-all@01.org>
Subject: Re: [PATCH ipsec-next] pfkey: fix SADB_X_EXT_FILTER length check
Date: Fri, 21 Feb 2014 07:51:39 +0100 [thread overview]
Message-ID: <20140221065139.GG32371@secunet.com> (raw)
In-Reply-To: <1392904361-11127-1-git-send-email-nicolas.dichtel@6wind.com>
On Thu, Feb 20, 2014 at 02:52:41PM +0100, Nicolas Dichtel wrote:
> This patch fixes commit d3623099d350 ("ipsec: add support of limited SA dump").
>
> sadb_ext_min_len array should be updated with the new type (SADB_X_EXT_FILTER).
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Thanks for the quick fix, applied to ipsec-next.
prev parent reply other threads:[~2014-02-21 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140220100735.GA25752@elgon.mountain>
2014-02-20 13:52 ` [PATCH ipsec-next] pfkey: fix SADB_X_EXT_FILTER length check Nicolas Dichtel
2014-02-21 6:51 ` Steffen Klassert [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=20140221065139.GG32371@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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).