From: Mathias Krause <minipli@grsecurity.net>
To: Luiz Capitulino <luizcap@amazon.com>,
Sven-Haegar Koch <haegar@sdinet.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Bhatnagar, Rishabh" <risbhat@amazon.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"sashal@kernel.org" <sashal@kernel.org>,
abuehaze@amazon.com,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Observing RCU stalls in kernel 5.4/5.10/5.15/6.1 stable trees
Date: Wed, 14 Jun 2023 16:30:03 +0200 [thread overview]
Message-ID: <23fb8ad7-beb0-ae1c-fa5a-a682a57f79b0@grsecurity.net> (raw)
In-Reply-To: <f5d2cc62-4aae-2579-1468-2e6e389f28dc@amazon.com>
On 14.06.23 15:57, Luiz Capitulino wrote:
> On 2023-06-14 09:45, Sven-Haegar Koch wrote:
>> May be this, talking about the same commit as cause as this thread:
>>
>> Subject: Re: [PATCH] timekeeping: Align tick_sched_timer() with the HZ
>> tick. -- regression report
>> https://lore.kernel.org/lkml/5a56290d-806e-b9a5-f37c-f21958b5a8c0@grsecurity.net/
>
> Thank you, Sven.
>
> Sebastian, except for the detailed analysis which we haven't done yet, the
> issue described by Mathias matches 100% what we're observing. Also, we do
> observe this on bare-metal instances which could mean that the initial
> reports are against VMs because those are rebooted more often (our quick
> reproducer boots hundreds of instances in AWS and only 1 or 2 reproduces
> this).
Yeah, we're doing VM based testing more often than bare metal -- less so
on a AWS scale. That's why we observed it first in VMs. But that wasn't
meant to exclude bare metal, not at all. It's just, that we haven't
tried hard enough yet and testing VMs is so much more pleasant when it
comes to debugging boot issues ;)
Thanks,
Mathias
> IMHO, I'd suggest we revert this for now from Linus tree and stable trees.
> We can help testing for the fix maybe for the next merge window.
>
> - Luiz
>
next prev parent reply other threads:[~2023-06-14 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 18:49 Bhatnagar, Rishabh
2023-06-13 18:58 ` Bhatnagar, Rishabh
2023-06-14 9:14 ` gregkh
2023-06-14 13:08 ` Luiz Capitulino
2023-06-14 9:14 ` gregkh
2023-06-14 9:20 ` Sebastian Andrzej Siewior
2023-06-14 13:10 ` Luiz Capitulino
2023-06-14 13:45 ` Sven-Haegar Koch
2023-06-14 13:57 ` Luiz Capitulino
2023-06-14 14:30 ` Mathias Krause [this message]
2023-06-15 9:18 ` [PATCH] tick/common: Align tick period during sched_timer setup Sebastian Andrzej Siewior
2023-06-15 11:13 ` Mathias Krause
2023-06-15 12:20 ` Richard W.M. Jones
2023-06-15 14:15 ` Luiz Capitulino
2023-06-15 16:00 ` SeongJae Park
2023-06-19 6:18 ` Greg KH
2023-06-19 7:03 ` Mathias Krause
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=23fb8ad7-beb0-ae1c-fa5a-a682a57f79b0@grsecurity.net \
--to=minipli@grsecurity.net \
--cc=abuehaze@amazon.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=haegar@sdinet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luizcap@amazon.com \
--cc=risbhat@amazon.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®