All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
	vschneid@redhat.com, kernel-team@android.com,
	Derek Dolney <z23@posteo.net>,
	peterz@infradead.org
Subject: Re: [PATCH v5] cpu/hotplug: Do not bail-out in DYING/STARTING sections
Date: Tue, 27 Sep 2022 11:05:56 +0100	[thread overview]
Message-ID: <YzLLBBRiwuQnD2zc@google.com> (raw)
In-Reply-To: <42237005-5a6e-9462-bfdd-f1ba0c725c72@leemhuis.info>

On Tue, Sep 20, 2022 at 11:59:06AM +0200, Thorsten Leemhuis wrote:
> On 17.08.22 11:46, Thorsten Leemhuis wrote:
> > 
> > Hi, this is your Linux kernel regression tracker.
> > 
> > On 25.07.22 11:59, Vincent Donnefort wrote:
> >> The DYING/STARTING callbacks are not expected to fail. However, as reported
> >> by Derek, drivers such as tboot are still free to return errors within
> >> those sections, which halts the hot(un)plug and leaves the CPU in an
> >> unrecoverable state.
> >>
> >> No rollback being possible there, let's only log the failures and proceed
> >> with the following steps. This restores the hotplug behaviour prior to
> >> commit 453e41085183 ("cpu/hotplug: Add cpuhp_invoke_callback_range()")
> >>
> >> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215867
> >> Fixes: 453e41085183 ("cpu/hotplug: Add cpuhp_invoke_callback_range()")
> >> Reported-by: Derek Dolney <z23@posteo.net>
> >> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
> >> Tested-by: Derek Dolney <z23@posteo.net>
> > 
> > What's the status here? Did that patch to fixing a regression fall
> > through the cracks? It looks like nothing happened for 3 weeks now,
> > that's why I wondered, but maybe I missed something.
> 
> Hmm, Vincent seems to be MIA, at least I see no recent messages from him
> on lore. Odd. But well, it's still a fix for a regression and it's up to
> v5 already; Valentin already added his Reviewed-by, too. Would be a
> shame to waste this.
> 
> Thomas, could you maybe take a look at the patch?  Maybe we're lucky and
> the patch is already good to go...
> 
> Ciao, Thorsten
> 
> #regzbot poke

Hi Thorsten,

AFAIK, this patch is still valid. I don't think I do have any further action on
that though.

[...]

  reply	other threads:[~2022-09-27 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  9:59 [PATCH v5] cpu/hotplug: Do not bail-out in DYING/STARTING sections Vincent Donnefort
2022-07-25 15:07 ` Valentin Schneider
2022-07-25 15:16   ` Vincent Donnefort
2022-08-17  9:46 ` Thorsten Leemhuis
2022-09-20  9:59   ` Thorsten Leemhuis
2022-09-27 10:05     ` Vincent Donnefort [this message]
2022-09-27 10:20       ` 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=YzLLBBRiwuQnD2zc@google.com \
    --to=vdonnefort@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=regressions@leemhuis.info \
    --cc=tglx@linutronix.de \
    --cc=vschneid@redhat.com \
    --cc=z23@posteo.net \
    /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.