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 02044C433FE for ; Thu, 5 May 2022 14:00:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233206AbiEEODp (ORCPT ); Thu, 5 May 2022 10:03:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53818 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353382AbiEEODo (ORCPT ); Thu, 5 May 2022 10:03:44 -0400 Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B16D95643C for ; Thu, 5 May 2022 06:59:58 -0700 (PDT) Received: by mail-ed1-x529.google.com with SMTP id ba17so5322236edb.5 for ; Thu, 05 May 2022 06:59:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8cdP+QQ3RkXNjtwvBi4VN1FsvGgtTlKBfCuL8UUAtAI=; b=E8qBemq4oTx4YPbWRWMJzV2qIbcvYOdveNbfeZemz+4dZQ+I0m7fLXmsY75j+/wiX5 XaE1LThAuxmxZgvbTboIF71ZZ5XDfPUtgSQz8ZVQ2PL1AE4CxYt/PmItFNePGMLFoNgb A8tRUVmKiVc6KZIJU/kk/0DlACH0+77UO+Qz0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8cdP+QQ3RkXNjtwvBi4VN1FsvGgtTlKBfCuL8UUAtAI=; b=foEB+3rHgPSfqNXeMbKOoJ/QL+XFbz7FWlfcYd3hvrC+E+I6kL/EzpqyhnFutLxl3F E8qmVYLafDgZJ8kneQkQz/lb0q0gDtXi4IN53eH2RGqZqx963WQTgszP2YBp1QxMVEPm vMUjDihcNo1cIBRBHbmhbsn4JwmjWdKIZhBn46euQ2E0BDcAOnPLVXE5G5slBKrciUnV F9c6e6vP2F+ZEyoUJq2tmYajFUIV220YxG3LRuj9gIhQzmUiwddD9wBfpkYImvxKRtzT BiXquUttlxAdiJqL8UgSYyoUKCyhuV2LH9hczkiA4irNzMprL9X2lj+j1mX4ea6mgvW4 HuWA== X-Gm-Message-State: AOAM5304e3efO7D0Lzk2KDg4a8xlPcX7EzoYcbXa3OKg5Cl5UEabIqNO Goc0YqprluvpUdwquhNraFd+Zpk/KWQ1sOx1guzX2A== X-Google-Smtp-Source: ABdhPJzTe+CDKCcscUgOgvXLSyK5NVYs7EmJWj3tio4m59arkqFAPKBq+XxNeijdGRs92739wL1GOOxDMjNo+9z+bh8= X-Received: by 2002:a05:6402:5ca:b0:423:f330:f574 with SMTP id n10-20020a05640205ca00b00423f330f574mr30384732edx.116.1651759197275; Thu, 05 May 2022 06:59:57 -0700 (PDT) MIME-Version: 1.0 References: <20220505123033.sgcyx7kfl4kcfcds@ws.net.home> In-Reply-To: <20220505123033.sgcyx7kfl4kcfcds@ws.net.home> From: Miklos Szeredi Date: Thu, 5 May 2022 15:59:45 +0200 Message-ID: Subject: Re: [RFC PATCH] getting misc stats/attributes via xattr API To: Karel Zak Cc: linux-fsdevel@vger.kernel.org, Dave Chinner , "Theodore Ts'o" , 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 Thu, 5 May 2022 at 14:30, Karel Zak wrote: > Is there a way how to get mountinfo-like entry by mount ID for some > sub-tree? Something like: > > getfattr -etext -n ":mnt:info:21" / Yes: getfattr -etext -n ":mntns:21:info" / > > The interface has to be consistent with some notification system (I > see your question about fsnotify/fanotify at linux-fsdevel) and mount > ID seems better than paths due to over-mounts, etc. Right. If the mount notification doesn't fit into fsnotify well, the original patch from David could be used. I think that part was uncontroversial. Thanks, Miklos