From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 98F2DC43217 for ; Mon, 14 Nov 2022 12:36:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237185AbiKNMgN (ORCPT ); Mon, 14 Nov 2022 07:36:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56952 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237179AbiKNMgK (ORCPT ); Mon, 14 Nov 2022 07:36:10 -0500 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C12F4248E1 for ; Mon, 14 Nov 2022 04:36:06 -0800 (PST) Received: by mail-ej1-x62d.google.com with SMTP id f5so27956370ejc.5 for ; Mon, 14 Nov 2022 04:36:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sU9x5ssg8XOYMe/rb8up2J+YLGp3IkvlIELqEyeyXlY=; b=NnWstm8DqlCqRdyMglLY7MPEfHjK68m/pRvlqV3oel5H8vqtXc3KtfhohAcqmB6ke5 xIAoh3nDcghJ7DPQkq4B4QYfHnEbnKMgkpttObeK4MFq+jiRO5xIZJyJsZycus/ajUhU sEgbjUbiNBPFKDfWaa/cDrm/umRrNjbBJ3XBY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sU9x5ssg8XOYMe/rb8up2J+YLGp3IkvlIELqEyeyXlY=; b=HSo4OW7MfV6IY1+MNqGbueEtLhsck+TvSP1sKdZd2Brmm/XquWTqIN4NWnvRDbaOje ZUJOZuSuI/O5C34mfGZXsYFMUXOvlQV6wJSo1dbbXwieZ2y1qd8gR7r6vgJyUlWFUVeg YA/sjpC+uo62Auvoz7/CNehC4riPUOR2qkS9BnTu22KnviT7VuXxhTHs/qLZKIIoUy8J HInzSwpV5hJ1Zum8IH2sM+864ALN6jgC8LmRMbVHjU8xFpaQQQRBDEqryPwf7ehVQ2TW YfQIw7jWSZELnUr34eyEREYPNrPnIt2ZxC5TEcomiwTA2z+x+jEE44+hfbmgl8ey2MrP +T9Q== X-Gm-Message-State: ANoB5plUmWtcjh30cy87pX4VMXhoFPVVOE9L/A2bLlSyIi0whtQhNkvp +nRDzVelbZMEbWWI7o76sUJH+RZaabQsZ1x8jwuIoA== X-Google-Smtp-Source: AA0mqf7xxaXCQcsg9ZYGxFJ3RjLGgBQ3wnQMAUrceAXa9Wi66rhSV8regTVEEtLmw7PnnQh0JiI+9kMluq/F6yfI28I= X-Received: by 2002:a17:906:a044:b0:7a5:a671:8236 with SMTP id bg4-20020a170906a04400b007a5a6718236mr10321692ejb.187.1668429365397; Mon, 14 Nov 2022 04:36:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Miklos Szeredi Date: Mon, 14 Nov 2022 13:35:54 +0100 Message-ID: Subject: Re: [RFC PATCH] getting misc stats/attributes via xattr API To: Abel Wu Cc: linux-fsdevel@vger.kernel.org, Dave Chinner , "Theodore Ts'o" , Karel Zak , Greg KH , Christian Brauner , linux-kernel@vger.kernel.org, Linux API , linux-man , LSM , Ian Kent , David Howells , Linus Torvalds , Al Viro , Christian Brauner , Amir Goldstein , James Bottomley Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, 14 Nov 2022 at 10:00, Abel Wu 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