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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 1 Dec 2020 14:12:19 -0800 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Eric Sandeen <sandeen@...deen.net> Cc: Dave Chinner <david@...morbit.com>, "Darrick J. Wong" <darrick.wong@...cle.com>, Eric Sandeen <sandeen@...hat.com>, Miklos Szeredi <mszeredi@...hat.com>, Ira Weiny <ira.weiny@...el.com>, David Howells <dhowells@...hat.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-man <linux-man@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, xfs <linux-xfs@...r.kernel.org>, Ext4 Developers List <linux-ext4@...r.kernel.org>, Xiaoli Feng <xifeng@...hat.com> Subject: Re: [PATCH 2/2] statx: move STATX_ATTR_DAX attribute handling to filesystems On Tue, Dec 1, 2020 at 2:03 PM Eric Sandeen <sandeen@...deen.net> wrote: > > That's why I was keen to just add DAX unconditionally at this point, and if we want > to invent/refine meanings for the mask, we can still try to do that? Oh Gods. Let's *not* make this some "random filesystem choice" where now semantics depends on what some filesystem decided to do, and different filesystems have very subtly different semantics. This all screams "please keep this in the VFS layer" so that we at least have _one_ place where these kinds of decisions are made. I suspect very very few people actually end up caring about any of the STATX flags at all, of course. The fact that the DAX one was apparently entirely the wrong bit argues that this isn't all that important. Linus
Powered by blists - more mailing lists