netdev - Re: Having TIPC compiled in causes strange networking failures

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:   Sun, 26 May 2019 14:14:56 -0700
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     bepvte@...il.com
Cc:     hujunwei4@...wei.com,
        Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: Having TIPC compiled in causes strange networking failures

On Sat, May 25, 2019 at 5:27 PM <bepvte@...il.com> wrote:
>
> Hi! I build my own kernel, and I set TIPC as enabled long ago thinking
> it was something many applications depend on. After I upgraded to 5.1.5,
> I noticed lots of errors in my systemd log and that Firefox couldnt
> start any of its subprocesses:
>
> NET: Registered protocol family 30
> Failed to register TIPC socket type
>
> rtkit-daemon.service: Failed to set up network namespacing: File exists
>
> The "Failed to register" message was repeated many many times. Many
> other strange problems occured until I set TIPC to compile as a module
> instead. I believe this is a bug related to one of the recent TIPC
> commits.
>
> If you need any other debugging info or have somewhere else I should
> report this, let me know.

Probably this is caused by the same offending commit. So make sure you
have the revert of the offending commit:

commit 5593530e56943182ebb6d81eca8a3be6db6dbba4
Author: David S. Miller <davem@...emloft.net>
Date:   Fri May 17 12:15:05 2019 -0700

    Revert "tipc: fix modprobe tipc failed after switch order of
device registration"

    This reverts commit 532b0f7ece4cb2ffd24dc723ddf55242d1188e5e.

    More revisions coming up.

    Signed-off-by: David S. Miller <davem@...emloft.net>


A rework of the offending commit is commit 526f5b851a96 in upstream.

Thanks.