From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Chen Yu <yu.c.chen@intel.com>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] timekeeping: Fix memory overwrite of sleep_time_bin array
Date: Tue, 19 Jul 2016 00:01:37 +0200 [thread overview]
Message-ID: <1938295.fBmZlflNpk@vostro.rjw.lan> (raw)
In-Reply-To: <1468806139-31436-1-git-send-email-yu.c.chen@intel.com>
On Monday, July 18, 2016 09:42:19 AM Chen Yu wrote:
> It is reported the hibernation fails at 2nd attempt, which
> hangs at hibernate() -> syscore_resume() -> i8237A_resume()
> -> claim_dma_lock(), because the lock has already been taken.
> However there is actually no other process would like to grab
> this lock on that problematic platform.
>
> Further investigation shows that, the problem is caused by setting
> /sys/power/pm_trace to 1 before the 1st hibernation, since once
> pm_trace is enabled, the rtc becomes an unmeaningful value after resumed,
> which might bring a significant long sleep time in timekeeping_resume,
> thus in tk_debug_account_sleep_time, the delta of timespec64 might
> exceed 32bit after commit 7d489d15ce4b ("timekeeping: Convert timekeeping
> core to use timespec64s"), thus if the bit31 happened set to 1, the
> fls might return 32 and then we add 1 to sleep_time_bin[32], which
> caused a memory overwritten. As System.map shows:
>
> ffffffff81c9d080 b sleep_time_bin
> ffffffff81c9d100 B dma_spin_lock
>
> Thus set the dma_spin_lock.val to 1, which caused this problem.
Nice catch!
> This patch fixes this issue by extending sleep_time_bin to 64, and
> use __fls to be fit for timespec64.
>
> Fixes: 7d489d15ce4b ("timekeeping: Convert timekeeping core to use timespec64s")
> Reported-and-tested-by: Janek Kozicki <cosurgi@gmail.com>
> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
> ---
> kernel/time/timekeeping_debug.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/time/timekeeping_debug.c b/kernel/time/timekeeping_debug.c
> index f6bd652..12b07d5 100644
> --- a/kernel/time/timekeeping_debug.c
> +++ b/kernel/time/timekeeping_debug.c
> @@ -23,14 +23,14 @@
>
> #include "timekeeping_internal.h"
>
> -static unsigned int sleep_time_bin[32] = {0};
> +static unsigned int sleep_time_bin[64] = {0};
>
> static int tk_debug_show_sleep_time(struct seq_file *s, void *data)
> {
> unsigned int bin;
> seq_puts(s, " time (secs) count\n");
> seq_puts(s, "------------------------------\n");
> - for (bin = 0; bin < 32; bin++) {
> + for (bin = 0; bin < 64; bin++) {
> if (sleep_time_bin[bin] == 0)
> continue;
> seq_printf(s, "%10u - %-10u %4u\n",
> @@ -69,6 +69,7 @@ late_initcall(tk_debug_sleep_time_init);
>
> void tk_debug_account_sleep_time(struct timespec64 *t)
> {
> - sleep_time_bin[fls(t->tv_sec)]++;
> + if (t->tv_sec > 0)
> + sleep_time_bin[__fls(t->tv_sec)]++;
But you could simply validate t->tv_sec here without extending sleeo_time_bin[]
and switching over to __fls(), couldn't you?
Thanks,
Rafael
next parent reply other threads:[~2016-07-18 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1468806139-31436-1-git-send-email-yu.c.chen@intel.com>
2016-07-18 22:01 ` Rafael J. Wysocki [this message]
2016-07-18 23:34 ` [PATCH] timekeeping: Fix memory overwrite of sleep_time_bin array Chen, Yu C
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=1938295.fBmZlflNpk@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yu.c.chen@intel.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