Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp966039pxv; Fri, 9 Jul 2021 13:39:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwZET2SZ8wD7/0YIt98tCfKoGgGYl1RFROhFnhxgS10bq01udmSNjhrlDHMPRQuSkplFuoP X-Received: by 2002:a17:906:dc0f:: with SMTP id yy15mr8710327ejb.255.1625863144184; Fri, 09 Jul 2021 13:39:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625863144; cv=none; d=google.com; s=arc-20160816; b=h3T4L2Opu65RRvJlN2JyqWe0XmlGcA0pKdn+uo8ggCsLzvX60v8H3PsyHhSgVNwAN/ ktIcpbofBTc7+lSJqs/jbYdw+L+zrJNAsuJhh+dx33Hlok84K3ytrBgbVuJejbdbRQGX Z6HUSy1/grww6zLojNGNUx1jMrnhV7kcUe+P+dDSOb9MTjBU5te/81a9HzIj0s5+pw8q +TxW0/kziHC0cTA+eU0oehNacTqJlzFaby/nR5ZsqNi4NpzYxrlPSSf0yNf3mstn/nBV vqYQsegPmUlLzjiRoKBx5nupwqiKfLF6B3JvI7biMCKirTXUQlQxs6hJMjmblLRw7c9e tVbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=ygOye1XRlX4PU3WjwjbVvOl5I1maVtqm+jdvQWOs9r0=; b=GrJqxhdqdBmHXdiWIAs9XS45O9Y4YRIvjOibWhfwxUBOzxC/0VdDigOeDa8aIwuJ/T cyN0BlR7yKgXEPj/SZrN7gNMKYw5t88kview89Y4pR5O8NB4YJ0Y7McsCU3faFUC7Z8T ev/5MyfUL8Hbr1LW4CMUcv8680o/XTnNjB2C9GtPBEXDj1RSA/Q94ABQP7qBzZnFC3mJ fpMS4s5YXi2LtTap6ZM2K2HjpCKLYtPvlIHC3iKTtpKezRhhiLJK6rZUHQtFvfDnrmP+ ApmlYBTDGL0G6SYyynDNW8KprXuyFsXF/8UdLii/MfW7ZfDCuCDhxTXVjVrBV4GjVZmF 6XPQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gs7si7601928ejc.609.2021.07.09.13.38.40; Fri, 09 Jul 2021 13:39:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230191AbhGIUjz (ORCPT + 99 others); Fri, 9 Jul 2021 16:39:55 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:45661 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S229506AbhGIUjz (ORCPT ); Fri, 9 Jul 2021 16:39:55 -0400 Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 169KaXOm025930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 9 Jul 2021 16:36:41 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 320F815C3C9E; Fri, 9 Jul 2021 16:36:33 -0400 (EDT) Date: Fri, 9 Jul 2021 16:36:33 -0400 From: "Theodore Ts'o" To: Casey Schaufler Cc: Vivek Goyal , Christian Brauner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, virtio-fs@redhat.com, dwalsh@redhat.com, dgilbert@redhat.com, casey.schaufler@intel.com, linux-security-module@vger.kernel.org, selinux@vger.kernel.org, miklos@szeredi.hu, gscrivan@redhat.com, jack@suse.cz, Christoph Hellwig Subject: Re: [PATCH v2 1/1] xattr: Allow user.* xattr on symlink and special files Message-ID: References: <20210708175738.360757-1-vgoyal@redhat.com> <20210708175738.360757-2-vgoyal@redhat.com> <20210709091915.2bd4snyfjndexw2b@wittgenstein> <20210709152737.GA398382@redhat.com> <710d1c6f-d477-384f-0cc1-8914258f1fb1@schaufler-ca.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <710d1c6f-d477-384f-0cc1-8914258f1fb1@schaufler-ca.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 09, 2021 at 08:34:41AM -0700, Casey Schaufler wrote: > >> One question, do all filesystem supporting xattrs deal with setting them > >> on symlinks/device files correctly? > > Wrote a simple bash script to do setfattr/getfattr user.foo xattr on > > symlink and device node on ext4, xfs and btrfs and it works fine. > > How about nfs, tmpfs, overlayfs and/or some of the other less conventional > filesystems? As a suggestion, perhaps you could take your bash script and turn it into an xfstests test so we can more easily test various file systems, both now and once the commit is accepted, to look for regressions? Cheers, - Ted