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: <173159220758.521904.15496365458938404053.b4-ty@mit.edu> Date: Thu, 14 Nov 2024 08:53:37 -0500 From: "Theodore Ts'o" <tytso@....edu> To: Andreas Dilger <adilger.kernel@...ger.ca>, Mathieu Othacehe <m.othacehe@...il.com> Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, lukas.skupinski@...disgyr.com, anton.reding@...disgyr.com Subject: Re: [PATCH 1/1] ext4: Prevent an infinite loop in the lazyinit thread. On Wed, 06 Nov 2024 14:47:41 +0100, Mathieu Othacehe wrote: > Use ktime_get_ns instead of ktime_get_real_ns when computing the lr_timeout > not to be affected by system time jumps. > > Use a boolean instead of the MAX_JIFFY_OFFSET value to determine whether > the next_wakeup value has been set. Comparing elr->lr_next_sched to > MAX_JIFFY_OFFSET can cause the lazyinit thread to loop indefinitely. > > [...] Applied, thanks! [1/1] ext4: Prevent an infinite loop in the lazyinit thread. commit: e06a8c24f6445c2f1b5255caa4f63b38e31c43fa Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists