archive mirror
 help / color / mirror / Atom feed
From: Patrick Schaaf <>
Subject: Re: stable 5.4.135 REGRESSION / once-a-day WARNING: at kthread_is_per_cpu+0x1c/0x20
Date: Tue, 31 Aug 2021 06:46:40 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Looking into this again.

Unfortunately, couldn't see how I would do bisection on the issue, as
it appears with that 5.4.118 commit implicated by the call stack,and
with tha tremoved,is obviously gone(that I tested, 5.4.135 with
b56ad4febe67b8c0647c0a3e427e935a76dedb59 reverted runs smoothly for
me, while the original 5.4.135 with that 5.4.118 time commit in, now
on a dozen machines, throws the WARNING.

I got email on the side of someone (Igor, on Cc) who sees the same
with DELL servers, a newer 5.10 kernel, for him running IPVS + he sees
actual operational impact there.

I just had a look at Linus mainlinetree, and see there is this
followup / further fix from Peter Zijlstra,
; now I'm much too incompetent to try and backport that, as it looks
more involved, but I imagine such a backport would be needed to fix
the WARNING (or IPVS breakage of Igor) we see.

best regards

  parent reply	other threads:[~2021-08-31  4:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 17:02 stable 5.4.135 REGRESSION / once-a-day WARNING: at kthread_is_per_cpu+0x1c/0x20 bof
2021-07-28 17:45 ` Greg KH
2021-07-28 17:51   ` Patrick Schaaf
2021-08-31  4:46   ` Patrick Schaaf [this message]
2021-08-31  7:00     ` Peter Zijlstra
2021-08-31 14:57       ` Patrick Schaaf
2021-07-28 17:40 bof

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 \
    --in-reply-to='' \ \ \ \ \ \

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