linux-kernel - Re: Sync semantics.

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: <20101112071158.GG16758@myhost.felk.cvut.cz>
Date:	Fri, 12 Nov 2010 08:11:58 +0100
From:	Michal Svoboda <michal.svoboda@...nts.felk.cvut.cz>
To:	linux-kernel@...r.kernel.org
Subject: Re: Sync semantics.

Rogier Wolff wrote:
> What should I expect from a "sync" system call?
> # time sync
> 0.000u 0.220s 2:22:23.96 0.0%   0+0k 0+0io 2pf+0w
> Two hours 22 minutes. 

I would also be interested to hear the answer for this question. Sync
and ongoing i/o simply don't seem to play well together, and you don't
even need anything as heavy as mentioned above.

Michal Svoboda

Content of type "application/pgp-signature" skipped