linux-kernel - Re: two reports about NULL pointer dereferences in mm subsystem since 5.18(?) with qbittorrent on XFS

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: <d3320f6f-0f31-4894-713b-821f6e1e48ec@leemhuis.info>
Date:   Fri, 28 Jul 2023 14:01:52 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Matthew Wilcox <willy@...radead.org>,
        Linux regressions mailing list <regressions@...ts.linux.dev>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux-MM <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: two reports about NULL pointer dereferences in mm subsystem since
 5.18(?) with qbittorrent on XFS

On 26.07.23 16:54, Matthew Wilcox wrote:
> On Wed, Jul 26, 2023 at 02:43:24PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Hi everyone! There are two regression reports with somewhat similar
>> symptoms in bugzilla.kernel.org that seem to not get the attention they
>> IMHO deserve.
> 
> I'm sorry you think this regression hasn't received the attention that
> it deserves.  I've spent weeks thinking about this problem

I know, but my last mails to prod things a few weeks ago iirc didn't
even get any reply, that's why I got impatient and started this thread
once it was confirmed the bug is not fixed. I pretty sure that's
expected in my position at this point; looking back at this now in
contrast to how Linus usually handles regressions I wonder if I should
have gotten impatient a bit earlier, as this caused trouble for a quite
a few users for quite a while already. But whatever, that's water under
the bridge now.

> and trying to track it down, with no success so far.

I saw your comments in the bugzilla ticket, so it seems you finally
found something that might cause the reported problems. Great & many thx
for that!

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.