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: <a1b092fb-ddde-4126-8950-153239764e3d@I-love.SAKURA.ne.jp>
Date: Tue, 11 Jun 2024 23:27:08 +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:
> I fixed it up (I just used the former) and can carry the fix as
> necessary.

I updated "rtnetlink: print rtnl_mutex holder/waiter for debug purpose"
patch, and I think that you no longer need to carry the fix.

This patch already found a suspicious culprit, and I added
"net/sched: Sleep before rechecking index at tcf_idr_check_alloc()" patch as
https://sourceforge.net/p/tomoyo/tomoyo.git/ci/35a1fb207602fb5eacf6fe5b8a35456d5dabd631/
to see if hung task message still appears.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ