All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: stable@vger.kernel.org, paulmck@kernel.org, rcu@vger.kernel.org
Subject: Re: Please apply to v5.15 stable: 96017bf90397 ("rcu-tasks: Simplify trc_read_check_handler() atomic operations")
Date: Wed, 4 Jan 2023 13:34:52 +0100	[thread overview]
Message-ID: <Y7VybOrgufZLFcp5@kroah.com> (raw)
In-Reply-To: <CAEXW_YRRws7fAZfK_Um1F9LQBE5WOM_cE_TOk5s39C597HxeoA@mail.gmail.com>

On Wed, Dec 28, 2022 at 04:30:30AM +0000, Joel Fernandes wrote:
> On Wed, Dec 28, 2022 at 1:47 AM Joel Fernandes <joel@joelfernandes.org> wrote:
> >
> > Hello,
> >
> > Please apply 96017bf90397 ("rcu-tasks: Simplify trc_read_check_handler()
> > atomic operations") to the stable v5.15 stable kernel. It made it in v5.16.
> >
> > I confirmed the patch fixes the following splat which happens twice on TRACE02:
> >
> > [  765.941351] WARNING: CPU: 0 PID: 80 at kernel/rcu/tasks.h:895 trc_read_check_handler+0x61/0xe0
> > [  765.949880] Modules linked in:
> > [  765.953006] CPU: 0 PID: 80 Comm: rcu_torture_rea Not tainted 5.15.86-rc1+ #25
> > [  765.959982] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
> > [  765.967964] RIP: 0010:trc_read_check_handler+0x61/0xe0
> > [  765.973050] Code: 01 00 89 c0 48 03 2c c5 80 f8 a5 ae c6 45 00 00 [..]
> > [  765.991768] RSP: 0000:ffffa64ac0003fb0 EFLAGS: 00010047
> > [  765.997042] RAX: ffffffffad4f8610 RBX: ffffa26b41bd3000 RCX: ffffa26b5f4ac8c0
> > [  766.004418] RDX: 0000000000000000 RSI: ffffffffae978121 RDI: ffffa26b41bd3000
> > [  766.011502] RBP: ffffa26b41bd6000 R08: ffffa26b41bd3000 R09: 0000000000000000
> > [  766.018778] R10: 0000000000000000 R11: ffffa64ac0003ff8 R12: 0000000000000000
> > [  766.025943] R13: ffffa26b5f4ac8c0 R14: 0000000000000000 R15: 0000000000000000
> > [  766.034383] FS:  0000000000000000(0000) GS:ffffa26b5f400000(0000) knlGS:0000000000000000
> > [  766.042925] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [  766.048775] CR2: 0000000000000000 CR3: 0000000001924000 CR4: 00000000000006f0
> > [  766.055991] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [  766.063135] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > [  766.070711] Call Trace:
> > [  766.073515]  <IRQ>
> > [  766.075807]  flush_smp_call_function_queue+0xec/0x1a0
> > [  766.081087]  __sysvec_call_function_single+0x3e/0x1d0
> > [  766.086466]  sysvec_call_function_single+0x89/0xc0
> > [  766.091431]  </IRQ>
> > [  766.093713]  <TASK>
> > [  766.095930]  asm_sysvec_call_function_single+0x16/0x20
> >
> > Full kernel logs:
> > http://box.joelfernandes.org:9080/job/rcutorture_stable/job/Linux%20Stable%20RC%205.15/lastFailedBuild/artifact/tools/testing/selftests/rcutorture/res/2022.12.27-20.43.34/TRACE02/console.log
> 
> Updated link to full kernel log: https://hastebin.com/raw/uvoholebol


Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-01-04 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  1:47 Please apply to v5.15 stable: 96017bf90397 ("rcu-tasks: Simplify trc_read_check_handler() atomic operations") Joel Fernandes
2022-12-28  4:30 ` Joel Fernandes
2023-01-04 12:34   ` Greg KH [this message]

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=Y7VybOrgufZLFcp5@kroah.com \
    --to=greg@kroah.com \
    --cc=joel@joelfernandes.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --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.