linux-kernel - Re: [bisected] ext4 corruption on parisc since 6.12

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7551c27f-58d5-4e4b-ac7f-8d09be634104@bell.net>
Date: Tue, 3 Dec 2024 11:38:52 -0500
From: John David Anglin <dave.anglin@...l.net>
To: matoro <matoro_mailinglist_kernel@...oro.tk>
Cc: Magnus Lindholm <linmag7@...il.com>,
 Linux Parisc <linux-parisc@...r.kernel.org>, deller@...nel.org,
 Deller <deller@....de>, Sam James <sam@...too.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [bisected] ext4 corruption on parisc since 6.12

On 2024-12-02 2:45 p.m., John David Anglin wrote:
> I also have in config:
> CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
Here is a comment from <https://www.kernel.org/doc/Documentation/timers/timekeeping.txt>:

On SMP systems, it is crucial for performance that sched_clock() can be called
independently on each CPU without any synchronization performance hits.
Some hardware (such as the x86 TSC) will cause the sched_clock() function to
drift between the CPUs on the system. The kernel can work around this by
enabling the CONFIG_HAVE_UNSTABLE_SCHED_CLOCK option. This is another aspect
that makes sched_clock() different from the ordinary clock source.

Dave

-- 
John David Anglin  dave.anglin@...l.net