From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH 0/1] ipset patch for nf
Date: Fri, 28 Aug 2015 19:15:51 +0200 [thread overview]
Message-ID: <1440782152-21890-1-git-send-email-kadlec@blackhole.kfki.hu> (raw)
Hi Pablo,
Please apply the next bugfix patch against the nf tree.
- Dave Jones reported that KASan detected out of bounds access in hash:net*
types, which is fixed in the next patch
Thanks,
Jozsef
The following changes since commit 18e1db67e93ed75d9dc0d34c8d783ccf10547c2b:
netfilter: bridge: fix IPv6 packets not being bridged with CONFIG_IPV6=n (2015-08-19 21:21:41 +0200)
are available in the git repository at:
git://blackhole.kfki.hu/nf master
for you to fetch changes up to 6fe7ccfd77415a6ba250c10c580eb3f9acf79753:
netfilter: ipset: Out of bound access in hash:net* types fixed (2015-08-28 18:51:30 +0200)
----------------------------------------------------------------
Jozsef Kadlecsik (1):
netfilter: ipset: Out of bound access in hash:net* types fixed
net/netfilter/ipset/ip_set_hash_gen.h | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
kadlec@blackhole ~/git/nf $
next reply other threads:[~2015-08-28 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 17:15 Jozsef Kadlecsik [this message]
2015-08-28 17:15 ` [PATCH 1/1] netfilter: ipset: Out of bound access in hash:net* types fixed Jozsef Kadlecsik
2015-08-28 23:03 ` [PATCH 0/1] ipset patch for nf Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2016-02-24 20:19 Jozsef Kadlecsik
2016-03-08 19:44 Jozsef Kadlecsik
2016-03-10 18:28 ` Pablo Neira Ayuso
2016-03-16 21:02 Jozsef Kadlecsik
2016-03-21 21:37 ` Pablo Neira Ayuso
2017-09-23 21:37 Jozsef Kadlecsik
2020-02-18 12:19 Jozsef Kadlecsik
2024-06-17 9:18 Jozsef Kadlecsik
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=1440782152-21890-1-git-send-email-kadlec@blackhole.kfki.hu \
--to=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).