From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] Netfilter fixes for net-next
Date: Wed, 05 Oct 2016 20:26:12 -0400 (EDT) [thread overview]
Message-ID: <20161005.202612.688630151401011904.davem@davemloft.net> (raw)
In-Reply-To: <1475712469-17000-1-git-send-email-pablo@netfilter.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Thu, 6 Oct 2016 02:07:44 +0200
> This is a pull request to address fallout from previous nf-next pull
> request, only fixes going on here:
>
> 1) Address a potential null dereference in nf_unregister_net_hook()
> when becomes nf_hook_entry_head is NULL, from Aaron Conole.
>
> 2) Missing ifdef for CONFIG_NETFILTER_INGRESS, also from Aaron.
>
> 3) Fix linking problems in xt_hashlimit in x86_32, from Pai.
>
> 4) Fix permissions of nf_log sysctl from unpriviledge netns, from
> Jann Horn.
>
> 5) Fix possible divide by zero in nft_limit, from Liping Zhang.
>
> You can pull these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git
Pulled, thanks Pablo.
prev parent reply other threads:[~2016-10-06 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 0:07 [PATCH 0/5] Netfilter fixes for net-next Pablo Neira Ayuso
2016-10-06 0:07 ` [PATCH 1/5] netfilter: Fix potential null pointer dereference Pablo Neira Ayuso
2016-10-06 0:07 ` [PATCH 2/5] netfilter: accommodate different kconfig in nf_set_hooks_head Pablo Neira Ayuso
2016-10-06 0:07 ` [PATCH 3/5] netfilter: xt_hashlimit: Fix link error in 32bit arch because of 64bit division Pablo Neira Ayuso
2016-10-06 0:07 ` [PATCH 4/5] netfilter: fix namespace handling in nf_log_proc_dostring Pablo Neira Ayuso
2016-10-06 0:07 ` [PATCH 5/5] netfilter: nft_limit: fix divided by zero panic Pablo Neira Ayuso
2016-10-06 0:26 ` 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=20161005.202612.688630151401011904.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).