netdev - Re: setns() affecting other threads in 5.10.132 and 6.0

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YxWhFuwM1y28ZRGf@kroah.com>
Date:   Mon, 5 Sep 2022 09:11:18 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     David Laight <David.Laight@...lab.com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        Eric Dumazet <edumazet@...gle.com>
Subject: Re: setns() affecting other threads in 5.10.132 and 6.0

On Sun, Sep 04, 2022 at 02:05:20PM +0000, David Laight wrote:
> Sometime after 5.10.105 (5.10.132 and 6.0) there is a change that
> makes setns(open("/proc/1/ns/net")) in the main process change
> the behaviour of other process threads.

Can you use 'git bisect' to find the offending commit?

thanks,

greg k-h