netdev - Re: linux-next: manual merge of the tomoyo tree with the net-next tree

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: <32ed65af-8d7a-46c0-ae34-c082b60302bb@I-love.SAKURA.ne.jp>
Date: Tue, 11 Jun 2024 11:25:51 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
        David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>, Networking <netdev@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the tomoyo tree with the net-next
 tree

On 2024/06/11 10:20, Stephen Rothwell wrote:
> It looks like the tomoyo tree commit should just be completely dropped?

Thank you for notification.

I want a tree for testing orphaned patches (which nobody is willing to take,
and as a result bugs remain unfixed for years) before sending to Linus, and
a tree for testing debug patches (where nobody can debug without additional
code, and as a result bugs remain unfixed for years).

I am for now using the tomoyo tree for such purpose because linux-next tree
is tested by syzbot. I appreciate if network people can carry c2bfadd666b5
("rtnetlink: print rtnl_mutex holder/waiter for debug purpose") in one of
trees syzbot tests.