linux-kernel - Re: Device loses barrier support

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: <49389F81.1090306@sandeen.net>
Date:	Thu, 04 Dec 2008 21:26:57 -0600
From:	Eric Sandeen <sandeen@...deen.net>
To:	Mikulas Patocka <mpatocka@...hat.com>
CC:	Andi Kleen <andi@...stfloor.org>, Milan Broz <mbroz@...hat.com>,
	Andi Kleen <andi-suse@...stfloor.org>,
	linux-kernel@...r.kernel.org, Alasdair G Kergon <agk@...hat.com>,
	xfs@....sgi.com
Subject: Re: Device loses barrier support

Mikulas Patocka wrote:

> Another thing:
> 
> I'm wondering, where in fsync() does Linux wait for hardware disk cache to 
> be flushed? Isn't there a bug that fsync() will return before the cache is 
> flushed? I couldn't really find it. The last thing do_fsync calls is 
> filemap_fdatawait and it doesn't do cache flush (blkdev_issue_flush).

ext4, reiserfs, and xfs all call blkdev_issue_flush() in their ->fsync
file operations (or down that path).

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/