From: Florian Westphal <fw@strlen.de>
To: Ren Wei <n05ec@lzu.edu.cn>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org,
phil@nwl.cc, yuantan098@gmail.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, bird@lzu.edu.cn, royenheart@gmail.com
Subject: Re: [PATCH nf v4 1/1] bridge: br_netfilter: pin bridge device while NFQUEUE holds fake dst
Date: Sat, 6 Jun 2026 10:21:24 +0200 [thread overview]
Message-ID: <aiPYhDrNiGuyRtGo@strlen.de> (raw)
In-Reply-To: <cbc3a29c0654e8fcee30cb021d57883fed77fafc.1780630094.git.royenheart@gmail.com>
Ren Wei <n05ec@lzu.edu.cn> wrote:
> #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
> const struct sk_buff *skb = entry->skb;
> + struct dst_entry *dst = skb_dst(skb);
> + struct net_device *dev = NULL;
>
> if (nf_bridge_info_exists(skb)) {
> entry->physin = nf_bridge_get_physindev(skb, entry->state.net);
> @@ -92,6 +95,17 @@ static void __nf_queue_entry_init_physdevs(struct nf_queue_entry *entry)
> entry->physin = NULL;
> entry->physout = NULL;
> }
> +
> + if (entry->state.pf == NFPROTO_BRIDGE &&
> + nf_bridge_info_exists(skb) &&
Is this check redundant?
> + dst && (dst->flags & DST_FAKE_RTABLE))
... this should be enough. In which cases can we have
FAKE_RTABLE and !nf_bridge_info_exists() ?
> #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
> + dev_hold(entry->bridge_dev);
LGTM, however, in last iteration sashiko complained that dev_cmp() in
nfnetlink_queue.c should gain a bridge_dev->ifindev check so that entries
are reaped in case bridge goes down.
Could you send a v5 that adds this test? Everything else here LGTM.
prev parent reply other threads:[~2026-06-06 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 6:50 [PATCH nf v4 1/1] bridge: br_netfilter: pin bridge device while NFQUEUE holds fake dst Ren Wei
2026-06-06 8:21 ` Florian Westphal [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=aiPYhDrNiGuyRtGo@strlen.de \
--to=fw@strlen.de \
--cc=bird@lzu.edu.cn \
--cc=n05ec@lzu.edu.cn \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=royenheart@gmail.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.