[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegsVsnjUy2N+qO-j4ToScwev01AjwUA0Enp_DxroPQS30A@mail.gmail.com>
Date: Mon, 14 Nov 2022 13:35:54 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Abel Wu <wuyun.abel@...edance.com>
Cc: linux-fsdevel@...r.kernel.org, Dave Chinner <david@...morbit.com>,
"Theodore Ts'o" <tytso@....edu>, Karel Zak <kzak@...hat.com>,
Greg KH <gregkh@...uxfoundation.org>,
Christian Brauner <brauner@...nel.org>,
linux-kernel@...r.kernel.org,
Linux API <linux-api@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>,
LSM <linux-security-module@...r.kernel.org>,
Ian Kent <raven@...maw.net>,
David Howells <dhowells@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Christian Brauner <christian@...uner.io>,
Amir Goldstein <amir73il@...il.com>,
James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [RFC PATCH] getting misc stats/attributes via xattr API
On Mon, 14 Nov 2022 at 10:00, Abel Wu <wuyun.abel@...edance.com> wrote:
>
> Hi Miklos and anyone interested in this proposal, is there any update on
> this? Sorry that I didn't find any..
No update.
Which part are you interested in?
Getting mount attributes? Or a generic key-value retrieval and
storage interface?
For the first one there are multiple proposals, one of them is adding
a new system call using binary structs. The fsinfo(2) syscall was
deemed overdesigned and rejected. Something simpler would probably be
fairly uncontroversial.
As for the other proposal it seems like some people would prefer a set
of new syscalls, while some others would like to reuse the xattr
syscalls. No agreement seems to have been reached.
Also I think a notification system for mount related events is also a
much needed component. I've tried to explore using the fsnotify
framework for this, but the code is pretty convoluted and I couldn't
get prototype working.
Thanks,
Miklos
Powered by blists - more mailing lists