linux-kernel - Re: Latest RC causing web browser crash

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: <e503afb9-df36-5b98-6b1b-e1ad3a9d13a7@leemhuis.info>
Date:   Thu, 16 Feb 2023 12:10:28 +0100
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Chris McGimpsey-Jones <chrisjones.unixmen@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: Latest RC causing web browser crash

On 30.01.23 11:11, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
> On 28.01.23 02:14, Chris McGimpsey-Jones wrote:
>> Is anyone else with the latest RC having issues with Google Chrome
>> browser, causing it to crash after a couple of minutes?
> FWIW, this is unlikely to get any traction: nearly nobody reads the LKML
> anymore, hence it's unlikely that someone that can help will see it.

FWIW, I pointed to this problem in my weekly reports, but there was no
reaction. That sound like this is something rare which might only happen
on your machine.

Is the problem actually still occuring?

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.

>> I reverted (temporarily) back to Linux 6.1.0 and it's fine.
>> Tested a couple of times, the issue can be reproduced.
> 
> Are there any crash dumps that might indicate what might cause the problem?
> 
>> I don't know of the relationship between the kernel and web browser
>> and it seems odd the kernel would cause this problem, but there's no
>> disputing it is the cause as I can reproduce the issue.
> 
> Well, things like this don't happen frequently, but they do happen.
> Without more data it's just very hard to get to the root of this issue,
> as it could be caused by all sorts of things (mm and drm are two most
> likely suspects, but it could be something totally different).
> 
> Could you try to bisect the issue? There are various pages on the net
> that explain how to do that.