archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #adding (Thorsten Leemhuis)" <>
To: kernel test robot <>,
	Qi Zheng <>
	"Andrew Morton" <>,
	"Vlastimil Babka" <>, "Kirill Tkhai" <>,
	"Roman Gushchin" <>,
	"Christian König" <>,
	"David Hildenbrand" <>,
	"Davidlohr Bueso" <>,
	"Johannes Weiner" <>,
	"Michal Hocko" <>,
	"Muchun Song" <>,
	"Paul E. McKenney" <>,
	"Shakeel Butt" <>,
	"Yang Shi" <>,,,,,
	"Linux kernel regressions list" <>
Subject: Re: [linus:master] [mm] f95bdb700b: stress-ng.ramfs.ops_per_sec -88.8% regression
Date: Sun, 18 Jun 2023 12:59:52 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 23.05.23 03:35, kernel test robot wrote:
> Hello,
> kernel test robot noticed a -88.8% regression of stress-ng.ramfs.ops_per_sec on:
> commit: f95bdb700bc6bb74e1199b1f5f90c613e152cfa7 ("mm: vmscan: make global slab shrink lockless")
> master

To be sure Linus is aware of the pending revert before releasing -rc7,
let me add this to the list of tracked regressions:

#regzbot ^introduced f95bdb700bc6bb74e1199b1f5f90c613e152cfa7.
#regzbot title mm: problems with the SRCU changeover (two reverts pending)
#regzbot monitor:
#regzbot fix: Revert "mm: vmscan: make global slab shrink lockless"
#regzbot ignore-activity

Side note: "Revert "mm: vmscan: add shrinker_srcu_generation"" (also in
mm-hotfixes-unstable/next) is related. See

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.

           reply	other threads:[~2023-06-18 10:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).