All of lore.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: Thu, 30 Nov 2023 12:22:14 +0000	[thread overview]
Message-ID: <2023113012-humorous-marshy-3060@gregkh> (raw)
In-Reply-To: <CALk6Uxoq=f7ews1Beve3qW_38w0sw1fnpJvmwMDfxy9eM+1AmA@mail.gmail.com>

On Thu, Nov 30, 2023 at 10:07:03PM +1000, Ronald Monthero wrote:
> On Thu, Nov 30, 2023 at 12:08 AM Ronald Monthero
> <debug.penguin32@gmail.com> wrote:
> >
> > On Sat, Nov 25, 2023 at 2:10 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > 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?
> >
> > Hi Greg,
> > Sorry I notice my typo error 193 instead of 93. I have tested on the
> > 5.15.93-rt58  kernel.
> 
> Hi Greg,
> I used a 5.15.93 kernel
> - on arm32 bit platform I tested with 5.15.93-rt58 (rt kernel) ,  on
> real hardware - Freescale LS1021A, 32 bit Cortex A7 processor
> - on x86_64 platform I tested non rt kernel 5.15.93  -  virtual
> machine - qemu platform
> 
> Below is the build log after patch to kernel/rcu/tree.h on x86_64
> 
> linux-5.15.93$ make
>   CALL    scripts/checksyscalls.sh
>   CALL    scripts/atomic/check-atomics.sh
>   DESCEND objtool
>   DESCEND bpf/resolve_btfids
>   CHK     include/generated/compile.h
>   CC      kernel/rcu/tree.o                         <<<
>   AR      kernel/rcu/built-in.a                     <<<
>   AR      kernel/built-in.a
>   CHK     kernel/kheaders_data.tar.xz
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   AR      init/built-in.a
>   LD      vmlinux.o
>   MODPOST vmlinux.symvers
>   MODINFO modules.builtin.modinfo
>   GEN     modules.builtin
>   LD      .tmp_vmlinux.btf
>   BTF     .btf.vmlinux.bin.o
>   LD      .tmp_vmlinux.kallsyms1
> 
> < snipped >
> 
>   BTF [M] sound/usb/usx2y/snd-usb-usx2y.ko
>   BTF [M] sound/virtio/virtio_snd.ko
>   BTF [M] sound/x86/snd-hdmi-lpe-audio.ko
>   BTF [M] sound/xen/snd_xen_front.ko
>   BTF [M] virt/lib/irqbypass.ko
> linux-5.15.93$

I don't understand what you are showing here, sorry.

I do not have a working backport anywhere that I can see, that is what
we need.  As you seem to have one, can you please submit it?

Also note, if you are using the -rt kernel, that changes lots of stuff
that we know nothing about, please work with the -rt kernel developers
about that.

thanks,

greg k-h

  reply	other threads:[~2023-11-30 12:22 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
2023-11-29 14:08   ` Ronald Monthero
2023-11-30 12:07     ` Ronald Monthero
2023-11-30 12:22       ` Greg KH [this message]
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=2023113012-humorous-marshy-3060@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 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.