From: Lance Yang <lance.yang@linux.dev>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Lance Yang <ioworker0@gmail.com>,
kadlec@netfilter.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
coreteam@netfilter.org, linux-kernel@vger.kernel.org,
netfilter-devel@vger.kernel.org, Zi Li <zi.li@linux.dev>
Subject: Re: [RESEND PATCH 1/1] netfilter: load nf_log_syslog on enabling nf_conntrack_log_invalid
Date: Thu, 22 May 2025 10:05:54 +0800 [thread overview]
Message-ID: <1c21a452-e1f4-42e0-93c0-0c49e4612dcd@linux.dev> (raw)
In-Reply-To: <aC4aNCpZMoYJ7R02@strlen.de>
On 2025/5/22 02:23, Florian Westphal wrote:
> Lance Yang <lance.yang@linux.dev> wrote:
>>> There is no need for 'syslog' to be active for 'log_invalid' to be
>>> useful as long as the system in question has e.g. ulogd running
>>> and listening to nflog messages.
>>>
>>> If anything, the modprobe should be done only when no logger
>>> is registered.
>>
>> Yes, could we load the module only when no logger exists? Something
>> like:
>>
>> + if (nf_logger_find_get(NFPROTO_IPV4, NF_LOG_TYPE_LOG) != 0)
>> + request_module("%s", "nf_log_syslog");
>
> This function bumps the module refcount, so if the logger exists you
> would need to call nf_logger_put() too.
Ah, understood ;)
>
> I'd add a new, simpler helper, that only returns if any logger
> is active.
>
> bool nf_log_is_registered(int pf);
>
> or something like that.
Nice, thanks for jumping in! I'll hold until the helper lands, then
rebase and send the v2.
Thanks,
Lance
next prev parent reply other threads:[~2025-05-22 2:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 5:37 Lance Yang
2025-05-21 10:07 ` Pablo Neira Ayuso
2025-05-21 11:21 ` Florian Westphal
2025-05-21 15:21 ` Lance Yang
2025-05-21 18:23 ` Florian Westphal
2025-05-22 2:05 ` Lance Yang [this message]
2025-05-22 6:34 ` Florian Westphal
2025-05-22 6:53 ` Lance Yang
2025-05-22 13:14 ` Lance Yang
2025-05-22 13:19 ` Florian Westphal
2025-05-22 13:58 ` Lance Yang
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=1c21a452-e1f4-42e0-93c0-0c49e4612dcd@linux.dev \
--to=lance.yang@linux.dev \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=ioworker0@gmail.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=zi.li@linux.dev \
/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
all inboxes | Powered by JetHome®