All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux kernel regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Linux 6.2-rc5
Date: Sun, 22 Jan 2023 14:49:22 +0100	[thread overview]
Message-ID: <8ec65f01-89fe-bd6f-a2c2-f4dfc0555cc2@leemhuis.info> (raw)
In-Reply-To: <CAHk-=wg+E9tTCrSqBOxejUX11f8ebyRWQ+4exC=cmOEupX_d7Q@mail.gmail.com>

[CCing Vlastimil, akpm, and Greg]

On 22.01.23 01:44, Linus Torvalds wrote:
> Ok, so I thought we were back to normal after the winter holidays at
> rc4. Now, a week later, I think I was mistaken - we have fairly
> sizable rc5, so I suspect there was still pent up testing and fixes
> from people being off. [...]

Huh, a -rc on Saturday evening? That's unusual. But well, in that case I
can wait till tomorrow with my regression report, as it's too late for
the rc anyway. :-D

But nevertheless there is one thing I want to bring up, even if -rc5 is
already out: Vlastimil asked me explicitly to highlight ```Revert
"mm/compaction: fix set skip in fast_find_migrateblock"```[1] in my
weekly report[2], as me would prefer if that patch could head to
mainline and especially stable rather sooner than later. He wrote:

```I consider this serious enough to be fixed in mainline+stable ASAP,
hopefully in rc5, as it does hurt people using 6.1.```

See [3] and [4] for the regression reports.

Andrew merged that patch on the 13th[5]. The fix thus by now spend a few
days in linux-next. But that hasn't been the the case yet when Andrew
sent the latest -mm hotfixes to you on the 16th, that's why it's still
in mm.

It's too late now to get it included in -rc5, but maybe Greg is willing
to pick it up for the next stable cycle if you merge it to mainline
today. But obviously it's your decision if that's worth it. And yes,
ideally I should have asked Andrew to send a extra pull request your
way, but I was busy with other stuff and only saw Vlastimil a few hours
ago. :-/ Sorry.

Ciao, Thorsten

[1] https://lore.kernel.org/all/20230113173345.9692-1-vbabka@suse.cz/
[2]
https://lore.kernel.org/all/f47f69f9-7378-f18c-399b-b277c753532e@suse.cz/
[3] https://bugzilla.suse.com/show_bug.cgi?id=1206848
[4]
[5] https://lore.kernel.org/all/20230114041117.B372AC43392@smtp.kernel.org/

  parent reply	other threads:[~2023-01-22 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  0:44 Linux 6.2-rc5 Linus Torvalds
2023-01-22 11:51 ` Build regressions/improvements in v6.2-rc5 Geert Uytterhoeven
2023-01-22 13:49 ` Linux kernel regression tracking (Thorsten Leemhuis) [this message]
2023-01-22 19:17   ` Linux 6.2-rc5 Linus Torvalds
2023-01-22 21:51 ` Guenter Roeck

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=8ec65f01-89fe-bd6f-a2c2-f4dfc0555cc2@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.