linux-ext4 - Re: fstrim has no effect on a just-mounted filesystem

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:	Wed, 12 Mar 2014 19:10:42 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	"Richard W.M. Jones" <rjones@...hat.com>,
	Eric Sandeen <sandeen@...hat.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: fstrim has no effect on a just-mounted filesystem

Il 12/03/2014 11:17, Richard W.M. Jones ha scritto:
> Somewhere, the discard requests are disappearing in the stack (or more
> likely, being delayed).  blktrace/trace-cmd somehow forces them out.
> But fsync/sync/umount/sleep does not.  They might be stuck in qemu too ...

No, this I can be quite sure about.  QEMU sends them as soon as they are 
received in the SCSI layer.  If they were ill-formed, QEMU would fail 
them.  If they got stuck, sooner or later you'd not be able to do I/O 
anymore (there is a queue depth limit) and the guest would start getting 
timeouts.

Also, certainly blktrace would have no effect on QEMU.

Paolo
--
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