linux-ext4 - Re: [PATCH] e2fsck: do not allow initialized blocks pass i

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180628224556.GE8521@thunk.org>
Date:   Thu, 28 Jun 2018 18:45:56 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Andreas Dilger <adilger@...ger.ca>
Cc:     Lukas Czerner <lczerner@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] e2fsck: do not allow initialized blocks pass i_size

On Thu, Jun 28, 2018 at 04:20:48PM -0600, Andreas Dilger wrote:
> That's true for stock ext4, but as I mentioned in my other email, Lustre
> will allocate up to the PAGE_SIZE boundary because the RDMA will overwrite
> the whole page regardless of where i_size is, which results in blocks
> being allocated beyond i_size for PAGE_SIZE > blocksize.

But does an RDMA operation actually do a block allocation?  Really?
And if it is willing to do a block allocation, why is it not willing
to bump i_size?

						- Ted