linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Matthew Wilcox <willy@infradead.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: two reports about NULL pointer dereferences in mm subsystem since 5.18(?) with qbittorrent on XFS
Date: Fri, 28 Jul 2023 14:01:52 +0200	[thread overview]
Message-ID: <d3320f6f-0f31-4894-713b-821f6e1e48ec@leemhuis.info> (raw)
In-Reply-To: <ZMEzuqTOdT1EDApa@casper.infradead.org>

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.


      reply	other threads:[~2023-07-28 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 12:43 Linux regression tracking (Thorsten Leemhuis)
2023-07-26 14:54 ` Matthew Wilcox
2023-07-28 12:01   ` Thorsten Leemhuis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d3320f6f-0f31-4894-713b-821f6e1e48ec@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox