linux-ext4 - Re: [PATCH] ext3: enable cache flush in ext3_sync

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] [day] [month] [year] [list]

Message-ID: <20090908131006.GA25208@lst.de>
Date:	Tue, 8 Sep 2009 15:10:06 +0200
From:	Christoph Hellwig <hch@....de>
To:	Jan Kara <jack@...e.cz>
Cc:	Eric Sandeen <sandeen@...hat.com>, Christoph Hellwig <hch@....de>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext3: enable cache flush in ext3_sync_file

On Tue, Sep 08, 2009 at 03:04:38PM +0200, Jan Kara wrote:
> > Acked-by: Eric Sandeen <sandeen@...hat.com>
>   But would the patch below be better? When we force a transaction
> commit we don't have to flush caches again. Or am I missing something?

If you know that you really did issue a barrier for sure you don't have
to flush the cache again.  I don't know extN enough to easily figure out
how, but if this patch ensures that it's good.  Same scheme should also
apply to ext4.
--
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