public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ronald Monthero <debug.penguin32@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Backport submission - rcu: Avoid tracing a few functions executed in stop machine
Date: Fri, 24 Nov 2023 16:10:07 +0000	[thread overview]
Message-ID: <2023112431-matching-imperfect-1b76@gregkh> (raw)
In-Reply-To: <CALk6Uxo5ymxu_P_7=LnLZwTgjYbrdE7gzwyeQVxeR431SPuxyw@mail.gmail.com>

On Tue, Nov 21, 2023 at 12:09:38AM +1000, Ronald Monthero wrote:
> Dear stable maintainers,
> I like to indicate the oops encountered and request the below patch to
> be backported to v 5.15. The fix is important to avoid recurring oops
> in context of rcu detected stalls.
> 
> subject: rcu: Avoid tracing a few functions executed in stop machine
> commit  48f8070f5dd8
> Target kernel version   v 5.15
> Reason for Application: To avoid oops due to rcu_prempt detect stalls
> on cpus/tasks
> 
> Environment and oops context: Issue was observed in my environment on
> 5.15.193 kernel (arm platform). The patch is helpful to avoid the
> below oops indicated in [1] and [2]

As the patch does not apply cleanly, we need a working and tested
backport so we know to apply the correct version.

Can you please provide that as you've obviously already done this?

thanks,

greg k-h

  reply	other threads:[~2023-11-24 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 14:09 Backport submission - rcu: Avoid tracing a few functions executed in stop machine Ronald Monthero
2023-11-24 16:10 ` Greg KH [this message]
2023-11-29 14:08   ` Ronald Monthero
2023-11-30 12:07     ` Ronald Monthero
2023-11-30 12:22       ` Greg KH
2023-12-02  6:56   ` [PATCH] " Ronald Monthero
2023-12-02  7:46     ` Greg KH
2023-12-02  8:05       ` Ronald Monthero
2023-12-02  8:11   ` Ronald Monthero

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=2023112431-matching-imperfect-1b76@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=debug.penguin32@gmail.com \
    --cc=stable@vger.kernel.org \
    /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