linux-ext4 - Re: persistent preallocation

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]

Date:	Tue, 03 Aug 2010 15:18:28 +0400
From:	Dmitry Monakhov <dmonakhov@...nvz.org>
To:	Bo Brantén <bosse@....umu.se>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: persistent preallocation

Bo Brantén <bosse@....umu.se> writes:

> Hello,
>
> I have a question on the implementation of persistent preallocation,
> the reason to not return the disk block is because it can contain old
> data but I wonder if an implementation has to return zeros instead or
Please look at fallocate(2) syscall.
> if it could return any garbage as long as it is not _that_ garbage?
Off course it is not a garbage, it is old user's data which may be
very very useful (old passwords, cookies, and etc)for person who has
time to analyze it :)
>
> Bo Branten
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html