From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/8] netfilter: merge nf_log_proto modules
Date: Fri, 26 Mar 2021 15:35:24 +0100 [thread overview]
Message-ID: <20210326143524.GB26422@orbyte.nwl.cc> (raw)
In-Reply-To: <20210325172512.17729-1-fw@strlen.de>
Hi,
On Thu, Mar 25, 2021 at 06:25:04PM +0100, Florian Westphal wrote:
[...]
> Last patch allows to move log backend module load
> to nft_log to avoid a deadlock that can occur when request_module()
> is called with the nft transaction mutex held.
With this series applied, my reproducer doesn't lock up anymore. In
addition to that, neither iptables nor nftables testsuites seem unhappy
with the change. Hence:
Tested-by: Phil Sutter <phil@nwl.cc>
Thanks a lot,
Phil
next prev parent reply other threads:[~2021-03-26 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 17:25 [PATCH 0/8] netfilter: merge nf_log_proto modules Florian Westphal
2021-03-25 17:25 ` [PATCH 1/8] netfilter: nf_log_ipv4: rename to nf_log_syslog Florian Westphal
2021-03-25 17:25 ` [PATCH 2/8] netfilter: nf_log_arp: merge with nf_log_syslog Florian Westphal
2021-03-25 17:25 ` [PATCH 3/8] netfilter: nf_log_ipv6: " Florian Westphal
2021-03-25 17:25 ` [PATCH 4/8] netfilter: nf_log_netdev: " Florian Westphal
2021-03-25 17:25 ` [PATCH 5/8] netfilter: nf_log_bridge: " Florian Westphal
2021-03-25 17:25 ` [PATCH 6/8] netfilter: nf_log_common: " Florian Westphal
2021-03-25 17:25 ` [PATCH 7/8] netfilter: nf_log: add module softdeps Florian Westphal
2021-03-25 17:25 ` [PATCH 8/8] netfilter: nft_log: perform module load from nf_tables Florian Westphal
2021-03-26 14:35 ` Phil Sutter [this message]
2021-03-30 22:50 ` [PATCH 0/8] netfilter: merge nf_log_proto modules Pablo Neira Ayuso
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=20210326143524.GB26422@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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).