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: <20080219091608.1da174c1@crazy>
Date:	Tue, 19 Feb 2008 09:16:08 +0100
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	"Kyungmin Park" <kmpark@...radead.org>
Cc:	"Linux Filesystem Mailing List" <linux-fsdevel@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Question about synchronous write on SSD

Hi,

Le Tue, 19 Feb 2008 14:48:18 +0900,
"Kyungmin Park" <kmpark@...radead.org> a écrit :

> +               /* Write synchronous */
> +               bio->bi_rw |= (1 << BIO_RW_SYNC);

Adding BIO_RW_SYNC doesn't make generic_make_request() synchronous as
in "generic_make_request() returns only after write completion".
BIO_RW_SYNC only asks the I/O layer to unplug immediatly. But
generic_make_request() still returns before the completion of the I/O,
and the completion is notified asynchronously.

See:
 http://lxr.free-electrons.com/source/include/linux/bio.h#139

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ