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: <48421D65.8040301@lougher.demon.co.uk>
Date:	Sun, 01 Jun 2008 04:54:13 +0100
From:	Phillip Lougher <phillip@...gher.demon.co.uk>
To:	Arnd Bergmann <arnd@...db.de>
CC:	David Newall <davidn@...idnewall.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	hch@....de
Subject: Re: [RFC 0/7] [RFC] cramfs: fake write support

Arnd Bergmann wrote:
> On Saturday 31 May 2008, David Newall wrote:
>> I don't agree that it is nicer to do this in cramfs.  I prefer the
>> technique of union of a tmpfs over some other fs because a single
>> solution that works with all filesystems is better than re-implementing
>> the same idea in multiple filesystems.  Multiple implementations is a
>> recipe for bugs and feature mismatch.
> 
> You're right in principle, but unfortunately there is to date no working
> implementation of union mounts. Giving users the option of using an
> existing file system with a few tweaks can only be better than than
> forcing them to use hacks like unionfs.
> 

I tend to agree with Arnd Bergmann.  While I prefer the aesthetic 
cleanliness of stackable filesystems, the lack of proper stacking 
support in the Linux VFS makes other techniques necessary.  Unionfs is 
complex and for many embedded systems with constrained resources Unionfs 
adds a lot of extra overhead.

If I read the patches correctly, when a file page is written to, only 
that page gets copied into the page cache and locked, the other pages 
continue to be read off disk from cramfs?  With Unionfs a page write 
causes the entire file to be copied up to the r/w tmpfs and locked into 
the page cache causing unnecessary RAM overhead.

Phillip

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ