From: Stefano Brivio <sbrivio@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: Florian Westphal <fw@strlen.de>,
syzbot <syzbot+33e06702fd6cffc24c40@syzkaller.appspotmail.com>,
coreteam@netfilter.org, davem@davemloft.net,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in nf_nat_unregister_fn
Date: Sat, 18 Apr 2020 01:00:38 +0200 [thread overview]
Message-ID: <20200418010038.57d5e5cf@elisabeth> (raw)
In-Reply-To: <20200417213348.GC32392@breakpoint.cc>
Hillf,
On Fri, 17 Apr 2020 23:33:48 +0200
Florian Westphal <fw@strlen.de> wrote:
> Hillf Danton <hdanton@sina.com> wrote:
> > In case of failure to register NFPROTO_IPV4, unregister NFPROTO_IPV6
> > instead of ops->pf (== NFPROTO_INET).
Note that the patch you sent didn't reach any list you probably sent it
to (netfilter-devel, netdev, lkml). I'm seeing it just because Florian
answered.
This is probably the same issue we had with your openvswitch patch last
year. By the way, the IP address you used last time is now reported as
being "blocked" by:
zen.spamhaus.org
pbl.spamhaus.org
I guess vger might filter using Spamhaus lists (including their "PBL"),
which won't let your email through if you're running a mail server with
an dynamic IP address.
I don't support this practice, but this might be the issue. You can
quickly get an overview of blacklists your address might be on at e.g.:
http://www.anti-abuse.org/
--
Stefano
next prev parent reply other threads:[~2020-04-17 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 5:36 WARNING in nf_nat_unregister_fn syzbot
[not found] ` <20200417094250.21872-1-hdanton@sina.com>
2020-04-17 21:33 ` Florian Westphal
2020-04-17 23:00 ` Stefano Brivio [this message]
[not found] ` <20200418082832.8904-1-hdanton@sina.com>
2020-04-19 13:00 ` 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=20200418010038.57d5e5cf@elisabeth \
--to=sbrivio@redhat.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=hdanton@sina.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+33e06702fd6cffc24c40@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 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).