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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 6 Jul 2021 16:23:04 -0400 From: "Theodore Ts'o" <tytso@....edu> To: Lukas Czerner <lczerner@...hat.com> Cc: linux-ext4@...r.kernel.org, Dusty Mabe <dustymabe@...hat.com> Subject: Re: [PATCH] e2fsck: fix last mount/write time when e2fsck is forced On Mon, Jun 14, 2021 at 03:27:25PM +0200, Lukas Czerner wrote: > With commit c52d930f e2fsck is no longer able to fix bad last > mount/write time by default because it is conditioned on s_checkinterval > not being zero, which it is by default. > > One place where it matters is when other e2fsprogs tools require to run > full file system check before a certain operation. If the last mount > time is for any reason in future, it will not allow it to run even if > full e2fsck is ran. > > Fix it by checking the last mount/write time when the e2fsck is forced, > except for the case where we know the system clock is broken. > > Fixes: c52d930f ("e2fsck: don't check for future superblock times if checkinterval == 0") > Reported-by: Dusty Mabe <dustymabe@...hat.com> > Signed-off-by: Lukas Czerner <lczerner@...hat.com> Applied, thanks. - Ted
Powered by blists - more mailing lists