| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20211130162815.GU641268@paulmck-ThinkPad-P17-Gen-1>
Date: Tue, 30 Nov 2021 08:28:15 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Feng Tang <feng.tang@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...el.com>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
linux-kernel@...r.kernel.org, rui.zhang@...el.com,
andi.kleen@...el.com, len.brown@...el.com, tim.c.chen@...el.com
Subject: Re: [PATCH v3 2/2] x86/tsc: skip tsc watchdog checking for qualified
platforms
On Tue, Nov 30, 2021 at 11:02:56PM +0800, Feng Tang wrote:
> Hi Paul,
>
> Thanks for the review!
>
> On Tue, Nov 30, 2021 at 06:40:48AM -0800, Paul E. McKenney wrote:
> > On Tue, Nov 30, 2021 at 02:46:23PM +0800, Feng Tang wrote:
> > > On Wed, Nov 17, 2021 at 10:37:51AM +0800, Feng Tang wrote:
> > > > There are cases that tsc clocksources are wrongly judged as unstable by
> > > > clocksource watchdogs like hpet, acpi_pm or 'refined-jiffies'. While
> > > > there is hardly a general reliable way to check the validity of a
> > > > watchdog, and to protect the innocent tsc, Thomas Gleixner proposed [1]:
> > >
> > > Hi All,
> > >
> > > Some more update, last week we got report from validation team that
> > > the "tsc judged as unstable" happened on latest desktop platform,
> > > which has serial earlyprintk enabled, and the watchdog here is
> > > 'refined-jiffies' while hpet is disabled during the PC10 check. I
> > > tried severy other client platforms I can find: Kabylake, Icelake
> > > and Alderlake, and the mis-judging can be easily reproduced on
> > > Icelake and Alderlake (not on Kabylake). Which could be cued by
> > > this 2/2 patch.
> > >
> > > Also, today we got same report on a 2-sockets Icelake Server with
> > > 5.5 kernel, while the watchdog is 'hpet', and the system is running
> > > stressful big-data workload.
> >
> > Were these tests run with Waiman's latest patch series? The first
> > two of them are on RCU's "dev" branch.
>
> No, I haven't tried Waiman's patches, which are more about refining
> cs_watchdog_read() check, while these 2 cases are about the really
> big gap between watchog and cur_clocksource
>
> The error log of first client platform (5.15 kernel) is:
>
> [ 2.994266] clocksource: 'refined-jiffies' wd_nsec: 516032250 wd_now: fffedc09 wd_last: fffedb88 mask: ffffffff
> [ 2.998352] initcall irq_sysfs_init+0x0/0x97 returned 0 after 0 usecs
> [ 3.002266] clocksource: 'tsc-early' cs_nsec: 767553349 cs_now: 71a87fd2f cs_last: 6db4968ff mask: ffffffffffffffff
> [ 3.006266] calling dma_atomic_pool_init+0x0/0x152 @ 1
> [ 3.010266] clocksource: No current clocksource.
> [ 3.010267] tsc: Marking TSC unstable due to clocksource watchdog
>
> We can see the gap is 516 ms vs 767 ms, and the delta is 267 ms.
> And the root cause is with earlyprintk serial console enabled,
> the periodic timer interrupt is severely affected to be not
> accurate.
>
> And similar big gap between 'tsc' and 'hpet' is seen for the server
> case (5.5 kernel which doesn't have the cs_watchdog_read() patchset).
>
> [1196945.314929] clocksource: timekeeping watchdog on CPU67: Marking clocksource 'tsc' as unstable because the skew is too large:
> [1196945.314935] clocksource: 'hpet' wd_now: 25272026 wd_last: 2e9ce418 mask: ffffffff
> [1196945.314938] clocksource: 'tsc' cs_now: 95b400003fdf1 cs_last: 95ae7ed7c33f7 mask: ffffffffffffffff
> [1196945.314948] tsc: Marking TSC unstable due to clocksource watchdog
> [1196945.314977] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
> [1196945.314981] sched_clock: Marking unstable (1196945264804527, 50153181)<-(1196945399926576, -84962703)
> [1196945.316255] clocksource: Switched to clocksource hpet
>
> For this case, I don't have access to the HW and only have the
> dmesg log, from which it seems the watchdog timer has been postponed
> a very long time from running.
Thank you for the analysis!
One approach to handle this situation would be to avoid checking for
clock skew if the time since the last watchdog read was more than (say)
twice the desired watchdog spacing. This does leave open the question of
exactly which clocksource to use to measure the time between successive
clocksource reads. My thought is to check this only once upon entry to
the handler and to use the designated-good clocksource.
Does that make sense, or would something else work better?
Thanx, Paul
> Thanks,
> Feng
>
>
> > Thanx, Paul
> >
> > > Thanks,
> > > Feng
> > >
> > >
> > > > "I'm inclined to lift that requirement when the CPU has:
> > > >
> > > > 1) X86_FEATURE_CONSTANT_TSC
> > > > 2) X86_FEATURE_NONSTOP_TSC
> > > > 3) X86_FEATURE_NONSTOP_TSC_S3
> > > > 4) X86_FEATURE_TSC_ADJUST
> > > > 5) At max. 4 sockets
> > > >
> > > > After two decades of horrors we're finally at a point where TSC seems
> > > > to be halfway reliable and less abused by BIOS tinkerers. TSC_ADJUST
> > > > was really key as we can now detect even small modifications reliably
> > > > and the important point is that we can cure them as well (not pretty
> > > > but better than all other options)."
> > > >
> > > > As feature #3 X86_FEATURE_NONSTOP_TSC_S3 only exists on several generations
> > > > of Atom processor, and is always coupled with X86_FEATURE_CONSTANT_TSC
> > > > and X86_FEATURE_NONSTOP_TSC, skip checking it, and also be more defensive
> > > > to use maxim of 2 sockets.
> > > >
> > > > The check is done inside tsc_init() before registering 'tsc-early' and
> > > > 'tsc' clocksources, as there were cases that both of them had been
> > > > wrongly judged as unreliable.
> > > >
> > > > For more background of tsc/watchdog, there is a good summary in [2]
> > > >
> > > > [1]. https://lore.kernel.org/lkml/87eekfk8bd.fsf@nanos.tec.linutronix.de/
> > > > [2]. https://lore.kernel.org/lkml/87a6pimt1f.ffs@nanos.tec.linutronix.de/
> > > > Suggested-by: Thomas Gleixner <tglx@...utronix.de>
> > > > Signed-off-by: Feng Tang <feng.tang@...el.com>
> > > > ---
> > > > Change log:
> > > >
> > > > v3:
> > > > * rebased against 5.16-rc1
> > > > * refine commit log
> > > >
> > > > v2:
> > > > * Directly skip watchdog check without messing flag
> > > > 'tsc_clocksource_reliable' (Thomas)
> > > >
> > > > arch/x86/kernel/tsc.c | 22 ++++++++++++++++++----
> > > > 1 file changed, 18 insertions(+), 4 deletions(-)
> > > >
> > > > diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> > > > index 2e076a459a0c..389511f59101 100644
> > > > --- a/arch/x86/kernel/tsc.c
> > > > +++ b/arch/x86/kernel/tsc.c
> > > > @@ -1180,6 +1180,12 @@ void mark_tsc_unstable(char *reason)
> > > >
> > > > EXPORT_SYMBOL_GPL(mark_tsc_unstable);
> > > >
> > > > +static void __init tsc_skip_watchdog_verify(void)
> > > > +{
> > > > + clocksource_tsc_early.flags &= ~CLOCK_SOURCE_MUST_VERIFY;
> > > > + clocksource_tsc.flags &= ~CLOCK_SOURCE_MUST_VERIFY;
> > > > +}
> > > > +
> > > > static void __init check_system_tsc_reliable(void)
> > > > {
> > > > #if defined(CONFIG_MGEODEGX1) || defined(CONFIG_MGEODE_LX) || defined(CONFIG_X86_GENERIC)
> > > > @@ -1196,6 +1202,17 @@ static void __init check_system_tsc_reliable(void)
> > > > #endif
> > > > if (boot_cpu_has(X86_FEATURE_TSC_RELIABLE))
> > > > tsc_clocksource_reliable = 1;
> > > > +
> > > > + /*
> > > > + * Ideally the socket number should be checked, but this is called
> > > > + * by tsc_init() which is in early boot phase and the socket numbers
> > > > + * may not be available. Use 'nr_online_nodes' as a fallback solution
> > > > + */
> > > > + if (boot_cpu_has(X86_FEATURE_CONSTANT_TSC) &&
> > > > + boot_cpu_has(X86_FEATURE_NONSTOP_TSC) &&
> > > > + boot_cpu_has(X86_FEATURE_TSC_ADJUST) &&
> > > > + nr_online_nodes <= 2)
> > > > + tsc_skip_watchdog_verify();
> > > > }
> > > >
> > > > /*
> > > > @@ -1387,9 +1404,6 @@ static int __init init_tsc_clocksource(void)
> > > > if (tsc_unstable)
> > > > goto unreg;
> > > >
> > > > - if (tsc_clocksource_reliable || no_tsc_watchdog)
> > > > - clocksource_tsc.flags &= ~CLOCK_SOURCE_MUST_VERIFY;
> > > > -
> > > > if (boot_cpu_has(X86_FEATURE_NONSTOP_TSC_S3))
> > > > clocksource_tsc.flags |= CLOCK_SOURCE_SUSPEND_NONSTOP;
> > > >
> > > > @@ -1527,7 +1541,7 @@ void __init tsc_init(void)
> > > > }
> > > >
> > > > if (tsc_clocksource_reliable || no_tsc_watchdog)
> > > > - clocksource_tsc_early.flags &= ~CLOCK_SOURCE_MUST_VERIFY;
> > > > + tsc_skip_watchdog_verify();
> > > >
> > > > clocksource_register_khz(&clocksource_tsc_early, tsc_khz);
> > > > detect_art();
> > > > --
> > > > 2.27.0
Powered by blists - more mailing lists