linux-kernel - Re: [RFC][PATCH] mm: write_cache

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Sep 2009 11:12:53 -0700
From:	Aaron Straus <aaron@...finllc.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Adrian Hunter <adrian.hunter@...ia.com>,
	"chris.mason@...cle.com" <chris.mason@...cle.com>,
	"david@...morbit.com" <david@...morbit.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Bityutskiy Artem (Nokia-D/Helsinki)" <Artem.Bityutskiy@...ia.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] mm: write_cache_pages be more sequential

On Sep 07 04:45 PM, Nick Piggin wrote:
> > I meant that only part of the page was written. e.g.
> > write 10240 bytes, wait for writeback, then write another
> > 10240 bytes.  The pages will be written out in the order
> > 0, 1, 2, 3, 4, 2
> 
> OK...
> 
> I guess it is a reasonable workaround for the problem. It is a bit
> unsatisfying to special case on a page basis like this, but anyway
> I don't think there should be a realistic downside in practice.

*NOTE* we also see this in NFS (I think) where a file is written to
sequentially yet readers will see holes in the file.

This is allowed behavior for NFS but annoying.  So a work-around would
be great!

					=a=


-- 
===================
Aaron Straus
aaron@...finllc.com

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