From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Andrew Morton <akpm@linux-foundation.org>,
decedion@gmail.com, mmp.dux@gmail.com
Cc: linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>
Subject: Bugzilla (was: Re: [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode))
Date: Tue, 22 Nov 2022 10:22:31 +0100 [thread overview]
Message-ID: <de276de8-885f-dbbe-7c80-455b92c8939c@leemhuis.info> (raw)
In-Reply-To: <20221121125400.334190a6d2791b0c9afbfea0@linux-foundation.org>
[removing bugzilla from the CC]
On 21.11.22 21:54, Andrew Morton wrote:
>
> Folks, thanks for continuing to work on this. But can I please please
> implore you to stop using bugzilla for this issue? We just don't use
> it and nobody looks at it so nobody knows what's going on.
That comment and something Willy recently said in another thread ("The
sooner kernel bug tracking switches to something useful like debbugs,
the better.") makes me wonder:
Are you two aware that the idea to slowly decommission bugzilla was
abandoned, as Konstantin plans changes to make it work better:
https://lore.kernel.org/lkml/20221017204731.a7rixhqlqmhlntvl@nitro.local/
Anyway, if you really dislike bugzilla that much, might it be a good
idea to ask Konstantin to remove or hide the "Memory Management" product
in bugzilla for now (I assume something like that is possible)? Maybe at
least some people will then go straight to the lists and don't expect to
find help in bugzilla.
Ciao, Thorsten
next prev parent reply other threads:[~2022-11-22 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216646-27@https.bugzilla.kernel.org/>
[not found] ` <bug-216646-27-o4jKola2S5@https.bugzilla.kernel.org/>
2022-11-21 20:54 ` [Bug 216646] having TRANSPARENT_HUGEPAGE enabled hangs some applications (supervisor read access in kernel mode) Andrew Morton
2022-11-22 9:22 ` Thorsten Leemhuis [this message]
2022-12-02 11:56 ` Thorsten Leemhuis
2022-12-02 16:58 ` Matthew Wilcox
2022-12-02 21:56 ` Mikhail Pletnev
2022-12-02 21:57 ` Matthew Wilcox
2022-12-02 22:44 ` Mikhail Pletnev
2022-12-05 20:25 ` Matthew Wilcox
2022-12-06 2:08 ` Mikhail Pletnev
2022-12-16 5:23 ` Thorsten Leemhuis
2023-02-24 10:21 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-24 18:08 ` Mikhail Pletenv
2023-03-14 10:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-17 11:12 ` Linux regression tracking (Thorsten Leemhuis)
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=de276de8-885f-dbbe-7c80-455b92c8939c@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=akpm@linux-foundation.org \
--cc=decedion@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mmp.dux@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).