linux-ext4 - Re: [PATCH v3 1/2] ext4: resize fs after resize

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: <YtrSK+qUm9+xRI7L@mit.edu>
Date:   Fri, 22 Jul 2022 12:36:59 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Zorro Lang <zlang@...hat.com>
Cc:     Sun Ke <sunke32@...wei.com>, fstests@...r.kernel.org,
        linux-ext4@...r.kernel.org
Subject: Re: [PATCH v3 1/2] ext4: resize fs after resize_inode without e2fsck

On Fri, Jul 22, 2022 at 11:11:14PM +0800, Zorro Lang wrote:
> > This resets the s_reserved_gdt_blocks field back to zero, so the fsck
> > doesn't fail.  Which is fine, because the point of the test is to see
> > whether the kernel dereferences a NULL pointer or not.
> 
> Or maybe just replace _reuqire_scratch with _require_scratch_nocheck, if we
> corrupt the fs on SCRATCH_DEV intentionally?

Agreed, that would be a better solution.

					- Ted