From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v2] printk: defer_console_output: use atomic update
Date: Mon, 14 Feb 2022 14:35:02 +0900 [thread overview]
Message-ID: <YgnqBgzEhgZZskun@google.com> (raw)
In-Reply-To: <YgnphtfTRBenHgfp@google.com>
On (22/02/14 14:32), Sergey Senozhatsky wrote:
> On (22/02/11 12:28), John Ogness wrote:
> > Hi Petr,
> >
> > On 2022-02-10, Petr Mladek <pmladek@suse.com> wrote:
> > > The patch has been committed into printk/linux.git, branch for-5.18.
> >
> > Sebastian also pointed out that the use of __this_cpu_xchg() is the same
> > problem with the same variable for the same reason. We should fold that
> > change into the patch as well. The patch will followup this message.
>
> But that __this_cpu_xchg() (that this lol) can only be performed form the
> IRQ context. Can you please elaborate what is the problem with it?
Oh, it can race with NMI, yeah.
prev parent reply other threads:[~2022-02-14 5:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 11:29 [PATCH] printk: defer_console_output: do not assume interrupts disabled John Ogness
2022-02-03 11:33 ` Sebastian Andrzej Siewior
2022-02-04 7:04 ` Sergey Senozhatsky
2022-02-07 9:46 ` [PATCH v2] printk: defer_console_output: use atomic update John Ogness
2022-02-10 15:47 ` Petr Mladek
2022-02-11 11:22 ` John Ogness
2022-02-11 11:23 ` [PATCH v3] printk: use atomic updates for klogd work John Ogness
2022-02-14 5:35 ` Sergey Senozhatsky
2022-02-15 15:26 ` Petr Mladek
2022-02-14 5:32 ` [PATCH v2] printk: defer_console_output: use atomic update Sergey Senozhatsky
2022-02-14 5:35 ` Sergey Senozhatsky [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=YgnqBgzEhgZZskun@google.com \
--to=senozhatsky@chromium.org \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox