linux-ext4 - Re: e2fsck: mark device inodes with EXT4_EXTENTS

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]

Date:   Sat, 23 Jun 2018 17:40:51 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Artem Blagodarenko <artem.blagodarenko@...il.com>
Cc:     linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca,
        alexey.lyashkov@...il.com
Subject: Re: e2fsck: mark device inodes with EXT4_EXTENTS_FL bad

On Thu, Jun 14, 2018 at 10:33:20AM +0300, Artem Blagodarenko wrote:
> From: Andreas Dilger <andreas.dilger@...el.com>
> 
> Mark device inodes bad if they have the EXT4_EXTENTS_FL set, since
> this should never happen and likely shows the inode is corrupt.
> 
> Change-Id: I85ab667b39ff57c658a779e59f692a080217690e
> Signed-off-by: Andreas Dilger <andreas.dilger@...el.com>

Thanks, applied.

One minor fixup: I updated the comment in pass1.c to reflect that we
are now testing the extents flag.

				- Ted