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: <307.1285589729@jrobl>
Date:	Mon, 27 Sep 2010 21:15:29 +0900
From:	"J. R. Okajima" <hooanon05@...oo.co.jp>
To:	Andreas Gruenbacher <agruen@...e.de>
Cc:	Miklos Szeredi <miklos@...redi.hu>,
	Valerie Aurora <vaurora@...hat.com>, linuxram@...ibm.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	neilb@...e.de, viro@...iv.linux.org.uk
Subject: Re: [PATCH 6/7 v3] overlay: hybrid overlay filesystem prototype


Andreas Gruenbacher:
> I can think of arguments for either behavior, perhaps with a slight preference 
> for your suggestion (default = opaque).
>
> In any case, admins will need a way to flip opaque flags and remove undesired 
> whiteouts.

Agreed.
Aufs is providing two options for this issue, "diropq=always" and
"diropq=whiteouted". Several years ago, the default was "always". But
soon it changed to "whiteouted" and I have never received objection
from users.
As for as I know, some users are happy since the number of whiteouts was
reduced. Because they merge layers manually for system
maintenance. Unnecessary whiteouts are not good to them.


J. R. Okajima
--
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