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-next>] [day] [month] [year] [list]
Message-ID: <f15ee051-2cfe-461f-991d-d09fd53bad4f@leemhuis.info>
Date: Wed, 21 Feb 2024 17:32:15 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: "Christian Brauner (Microsoft)" <brauner@...nel.org>,
 Alexander Viro <viro@...iv.linux.org.uk>
Cc: Matt Heon <mheon@...hat.com>, Ed Santiago <santiago@...hat.com>,
 Linux-fsdevel <linux-fsdevel@...r.kernel.org>,
 Paul Holzinger <pholzing@...hat.com>,
 Linux regressions mailing list <regressions@...ts.linux.dev>,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] 6.8-rc process is unable to exit and consumes a lot
 of cpu

[adding Al, Christian and a few lists to the list of recipients to
ensure all affected parties are aware of this new report about a bug for
which a fix is committed, but not yet mainlined]

Thread starts here:
https://lore.kernel.org/all/6a150ddd-3267-4f89-81bd-6807700c57c1@redhat.com/

On 21.02.24 16:56, Paul Holzinger wrote:
> Hi Thorsten,
> 
> On 21/02/2024 15:42, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 21.02.24 15:31, Paul Holzinger wrote:
>>> On 21/02/2024 15:20, Paul Holzinger wrote:
>>>> we are seeing problems with the 6.8-rc kernels[1] in our CI systems,
>>>> we see random process timeouts across our test suite. It appears that
>>>> sometimes a process is unable to exit, nothing happens even if we send
>>>> SIGKILL and instead the process consumes a lof of cpu.
>>> [...]
>> Thx for the report.
>>
>> Warning, this is not my area of expertise, so this might send you in the
>> totally wrong direction.
>>
>> I briefly checked lore for similar reports and noticed this one when I
>> searched for shrink_dcache_parent:
>>
>> https://lore.kernel.org/all/ZcKOGpTXnlmfplGR@gmail.com/
>
>> Do you think that might be related? A fix for this is pending in vfs.git.
>>
> yes that does seem very relevant. Running the sysrq command I get the
> same backtrace as the reporter there so I think it is fair to assume
> this is the same bug. Looking forward to get the fix into mainline.

FWIW, "the fix" afaics is 7e4a205fe56b90 ("Revert "get rid of
DCACHE_GENOCIDE"") sitting 'fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for more than
a week now.

I assume Al or Christian will send this to Linus soon. Christian in fact
already mentioned that he plans to send another vfs fix to Linux, but
that one iirc was sitting in another repo (but I might be mistaken there!).

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

P.S.: let me update regzbot while at it:

#regzbot introduced 57851607326a2beef21e67f83f4f53a90df8445a.
#regzbot fix: Revert "get rid of DCACHE_GENOCIDE"

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ