netdev - Re: WARNING in nf_nat_unregister

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 18 Apr 2020 01:00:38 +0200
From:   Stefano Brivio <sbrivio@...hat.com>
To:     Hillf Danton <hdanton@...a.com>
Cc:     Florian Westphal <fw@...len.de>,
        syzbot <syzbot+33e06702fd6cffc24c40@...kaller.appspotmail.com>,
        coreteam@...filter.org, davem@...emloft.net, kadlec@...filter.org,
        kuba@...nel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
        pablo@...filter.org, syzkaller-bugs@...glegroups.com
Subject: Re: WARNING in nf_nat_unregister_fn

Hillf,

On Fri, 17 Apr 2020 23:33:48 +0200
Florian Westphal <fw@...len.de> wrote:

> Hillf Danton <hdanton@...a.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