From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Benjamin Bara <bbara93@gmail.com>,
rafael.j.wysocki@intel.com, pmladek@suse.com
Cc: mcgrof@kernel.org, paulmck@kernel.org,
kai.heng.feng@canonical.com, tangmeng@uniontech.com,
john.ogness@linutronix.de, yuehaibing@huawei.com,
benjamin.bara@skidata.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/reboot: emergency_restart: set correct system_state
Date: Tue, 21 Mar 2023 05:12:19 +0300 [thread overview]
Message-ID: <58a254d6-5bf1-5474-3bc9-10d0c9f9a0cf@collabora.com> (raw)
In-Reply-To: <20230320213230.1459532-1-bbara93@gmail.com>
On 3/21/23 00:32, Benjamin Bara wrote:
> From: Benjamin Bara <benjamin.bara@skidata.com>
>
> As the emergency restart does not call kernel_restart_prepare(),
> the system_state stays in SYSTEM_RUNNING.
>
> This e.g. hinders i2c_in_atomic_xfer_mode() from becoming active,
> and therefore might lead to avoidable warnings in the restart handlers,
> e.g.:
> [ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0
> [ 12.676926] Voluntary context switch within RCU read-side critical section!
> ...
> [ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114
> [ 12.749179] wait_for_completion_timeout from tegra_i2c_wait_completion+0x40/0x70
> ...
> [ 12.994527] atomic_notifier_call_chain from machine_restart+0x34/0x58
> [ 13.001050] machine_restart from panic+0x2a8/0x32c
>
> Avoid these by setting the correct system_state.
>
> Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com>
> ---
> kernel/reboot.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/reboot.c b/kernel/reboot.c
> index 3bba88c7ffc6..6ebef11c8876 100644
> --- a/kernel/reboot.c
> +++ b/kernel/reboot.c
> @@ -74,6 +74,7 @@ void __weak (*pm_power_off)(void);
> void emergency_restart(void)
> {
> kmsg_dump(KMSG_DUMP_EMERG);
> + system_state = SYSTEM_RESTART;
> machine_emergency_restart();
> }
> EXPORT_SYMBOL_GPL(emergency_restart);
This patch needs to be paired with the i2c_in_atomic_xfer_mode() change.
Please also add the v5.2+ stable tag to the commit messages.
--
Best regards,
Dmitry
prev parent reply other threads:[~2023-03-21 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 21:32 Benjamin Bara
2023-03-21 2:12 ` Dmitry Osipenko [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=58a254d6-5bf1-5474-3bc9-10d0c9f9a0cf@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=bbara93@gmail.com \
--cc=benjamin.bara@skidata.com \
--cc=john.ogness@linutronix.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tangmeng@uniontech.com \
--cc=yuehaibing@huawei.com \
/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
all inboxes | Powered by JetHome®