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
| ||
|
Message-ID: <20190219040447.GX12668@bombadil.infradead.org> Date: Mon, 18 Feb 2019 20:04:47 -0800 From: Matthew Wilcox <willy@...radead.org> To: Andy Lutomirski <luto@...nel.org> Cc: Adam Borowski <kilobyte@...band.pl>, Boaz Harrosh <openosd@...il.com>, Dave Chinner <david@...morbit.com>, Omar Sandoval <osandov@...ndov.com>, Linux FS Devel <linux-fsdevel@...r.kernel.org>, Al Viro <viro@...iv.linux.org.uk>, kernel-team <kernel-team@...com>, Linux API <linux-api@...r.kernel.org>, Linux btrfs Developers List <linux-btrfs@...r.kernel.org>, Ext4 Developers List <linux-ext4@...r.kernel.org>, linux-f2fs-devel@...ts.sourceforge.net, linux-xfs@...r.kernel.org Subject: Re: [RFC PATCH 0/6] Allow setting file birth time with utimensat() On Sun, Feb 17, 2019 at 12:40:09PM -0800, Andy Lutomirski wrote: > So I'm highly in favor of this patch. If XFS wants to disallow > writing the birth time, fine, but I think that behavior should be > overridable. Please, no. We need to have consistent behaviour between at least Linux local filesystems. Not "Chris thinks this is a good idea, while Dave and Ted think its a bad idea, so btrfs supports it and XFS and ext4 disallow it".
Powered by blists - more mailing lists