linux-kernel - Re: Userspace woes with 5.1.5 due to TIPC

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]

Message-ID: <5498070b-c6e4-30e5-dea4-5767fe50f617@windriver.com>
Date:   Fri, 31 May 2019 19:13:43 +0800
From:   Ying Xue <ying.xue@...driver.com>
To:     Jon Maloy <jon.maloy@...csson.com>,
        Mihai Moldovan <ionic@...ic.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Userspace woes with 5.1.5 due to TIPC

On 5/31/19 7:02 PM, Jon Maloy wrote:
> This was the very reason the broken patch was introduced. AFAIK there is no problem after the corrected version of that patch was applied.

I have prepared for our patches on net-next tree. But when I checked my
patches on net tree, it's found that the issue has been fixed with
commit 526f5b851a96566803ee4bee60d0a34df56c77f8 ("tipc: fix modprobe
tipc failed after switch order of device registration"). There are four
commits which were introduced recently, and their names are quite
similar, and the fix is not merged into net-next tree, which makes me
misunderstood the issue status.

Anyway, it looks like failing to insert TIPC module has been resolved.
But I have not validated the fix by create multiple TIPC namespace, so I
am not sure whether it works normally.

Thanks,
Ying