From: Ross Zwisler <zwisler@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ring-buffer: Handle resize in early boot up
Date: Fri, 9 Dec 2022 11:32:52 -0700 [thread overview]
Message-ID: <Y5N/VM1u+Funtm0M@google.com> (raw)
In-Reply-To: <20221209131357.5e4f6d01@gandalf.local.home>
On Fri, Dec 09, 2022 at 01:13:57PM -0500, Steven Rostedt wrote:
> On Fri, 9 Dec 2022 09:57:48 -0700
> Ross Zwisler <zwisler@google.com> wrote:
>
> > > + if (cpu_id == smp_processor_id()) {
> > > + rb_update_pages(cpu_buffer);
> > > + migrate_enable();
> > > + } else {
> > > + migrate_enable();
> > > + schedule_work_on(cpu_id,
> > > + &cpu_buffer->update_pages_work);
> > > + wait_for_completion(&cpu_buffer->update_done);
> >
> > I ran with this patch on my test VM and hit the same Oops from the original
> > report.
> >
> > I think the problem is that we're still trying to enable interrupts via
> > wait_for_completion():
> >
> > wait_for_completion()
> > wait_for_common()
> > __wait_for_common()
> > raw_spin_unlock_irq()
> > _raw_spin_unlock_irq()
> > __raw_spin_unlock_irq()
> > local_irq_enable()
> >
> > I'm testing on a QEMU VM with 4 virtual CPUs, if that helps WRT where work is
> > being scheduled (cpu_id == smp_processor_id).
>
> Can you show the backtrace with that. Because when I triggered it, the
> other CPUs were not up and running. I'm testing this on a VM with 8 CPUs.
Ah, apologies, I think I got confused in my testing. It is indeed working for
me now.
Thank you for the fix!
Tested-by: Ross Zwisler <zwisler@google.com>
prev parent reply other threads:[~2022-12-09 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 15:11 [PATCH] ring-buffer: Handle resize in early boot up Steven Rostedt
2022-12-09 16:57 ` Ross Zwisler
2022-12-09 18:13 ` Steven Rostedt
2022-12-09 18:32 ` Ross Zwisler [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=Y5N/VM1u+Funtm0M@google.com \
--to=zwisler@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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.