From: Jianbo Liu <jianbol@nvidia.com>
To: "pablo@netfilter.org" <pablo@netfilter.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"fw@strlen.de" <fw@strlen.de>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [BUG] kernel warning from br_nf_local_in+0x157/0x180
Date: Mon, 1 Apr 2024 09:39:43 +0000 [thread overview]
Message-ID: <d134a3fb58c27abab012aa154401e403e6e46b84.camel@nvidia.com> (raw)
In-Reply-To: <ZgIkm3KNK78qpptx@calendula>
On Tue, 2024-03-26 at 02:28 +0100, Pablo Neira Ayuso wrote:
> On Sat, Mar 23, 2024 at 10:37:16AM +0000, Jianbo Liu wrote:
> > On Fri, 2024-03-22 at 13:27 +0100, Pablo Neira Ayuso wrote:
> > > Hi Jianbo,
> > >
> > > On Mon, Mar 18, 2024 at 09:41:46AM +0000, Jianbo Liu wrote:
> > > > Hi Florian and Pablo,
> > > >
> > > > We hit the following warning from br_nf_local_in+0x157/0x180.
> > >
> > > Can you give a try to this patch?
> > >
> >
> > Sorry, it doesn't fix.
> > It looks fine when running the test manually. But the warning still
> > appeared in our regression tests.
>
> You mean different test triggers now the warning splat?
It should be the same. The test I run manually was configured by the
scripts I posted in this thread.
>
> Not sure yet if this is the bug that is triggering the issue in your
> testbed yet, but I find it odd that packets hitting the local_in hook
> because promisc flag is set on can confirm conntrack entries.
>
This fix seems ok. I didn't see the warning or any other issue.
Thanks!
Jianbo
> Would you please give a try to this patch? Thanks!
prev parent reply other threads:[~2024-04-01 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:41 [BUG] kernel warning from br_nf_local_in+0x157/0x180 Jianbo Liu
2024-03-18 14:19 ` Florian Westphal
2024-03-22 12:27 ` Pablo Neira Ayuso
2024-03-23 10:37 ` Jianbo Liu
2024-03-26 1:28 ` Pablo Neira Ayuso
2024-04-01 9:39 ` Jianbo Liu [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=d134a3fb58c27abab012aa154401e403e6e46b84.camel@nvidia.com \
--to=jianbol@nvidia.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--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).