From: Jan Kara <jack@suse.cz>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Jann Horn <jannh@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 10/14] xattr,net: support limited amount of extended attributes on sockfs sockets
Date: Fri, 27 Feb 2026 16:25:14 +0100 [thread overview]
Message-ID: <nvbbdg5v2o5tzyzhzfpj2cyldsstgxsnwr7qfr36vwsyks7qjv@ey4qw2ut6q7z> (raw)
In-Reply-To: <20260216-work-xattr-socket-v1-10-c2efa4f74cb7@kernel.org>
On Mon 16-02-26 14:32:06, Christian Brauner wrote:
> Now that we've generalized the infrastructure for user.* xattrs make it
> possible to set up to 128 user.* extended attributes on a sockfs inode
> or up to 128kib. kernfs (cgroupfs) has the same limits and it has proven
> to be quite sufficient for nearly all use-cases.
>
> This will allow containers to label sockets and will e.g., be used by
> systemd and Gnome to find various sockets in containers where
> high-privilege or more complicated solutions aren't available.
>
> Signed-off-by: Christian Brauner <brauner@kernel.org>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> net/socket.c | 119 +++++++++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 92 insertions(+), 27 deletions(-)
>
> diff --git a/net/socket.c b/net/socket.c
> index 136b98c54fb3..7aa94fce7a8b 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -315,45 +315,70 @@ static int move_addr_to_user(struct sockaddr_storage *kaddr, int klen,
>
> static struct kmem_cache *sock_inode_cachep __ro_after_init;
>
> +struct sockfs_inode {
> + struct simple_xattrs *xattrs;
> + struct simple_xattr_limits xattr_limits;
> + struct socket_alloc;
> +};
> +
> +static struct sockfs_inode *SOCKFS_I(struct inode *inode)
> +{
> + return container_of(inode, struct sockfs_inode, vfs_inode);
> +}
> +
> static struct inode *sock_alloc_inode(struct super_block *sb)
> {
> - struct socket_alloc *ei;
> + struct sockfs_inode *si;
>
> - ei = alloc_inode_sb(sb, sock_inode_cachep, GFP_KERNEL);
> - if (!ei)
> + si = alloc_inode_sb(sb, sock_inode_cachep, GFP_KERNEL);
> + if (!si)
> return NULL;
> - init_waitqueue_head(&ei->socket.wq.wait);
> - ei->socket.wq.fasync_list = NULL;
> - ei->socket.wq.flags = 0;
> + si->xattrs = NULL;
> + simple_xattr_limits_init(&si->xattr_limits);
> +
> + init_waitqueue_head(&si->socket.wq.wait);
> + si->socket.wq.fasync_list = NULL;
> + si->socket.wq.flags = 0;
> +
> + si->socket.state = SS_UNCONNECTED;
> + si->socket.flags = 0;
> + si->socket.ops = NULL;
> + si->socket.sk = NULL;
> + si->socket.file = NULL;
>
> - ei->socket.state = SS_UNCONNECTED;
> - ei->socket.flags = 0;
> - ei->socket.ops = NULL;
> - ei->socket.sk = NULL;
> - ei->socket.file = NULL;
> + return &si->vfs_inode;
> +}
> +
> +static void sock_evict_inode(struct inode *inode)
> +{
> + struct sockfs_inode *si = SOCKFS_I(inode);
> + struct simple_xattrs *xattrs = si->xattrs;
>
> - return &ei->vfs_inode;
> + if (xattrs) {
> + simple_xattrs_free(xattrs, NULL);
> + kfree(xattrs);
> + }
> + clear_inode(inode);
> }
>
> static void sock_free_inode(struct inode *inode)
> {
> - struct socket_alloc *ei;
> + struct sockfs_inode *si = SOCKFS_I(inode);
>
> - ei = container_of(inode, struct socket_alloc, vfs_inode);
> - kmem_cache_free(sock_inode_cachep, ei);
> + kmem_cache_free(sock_inode_cachep, si);
> }
>
> static void init_once(void *foo)
> {
> - struct socket_alloc *ei = (struct socket_alloc *)foo;
> + struct sockfs_inode *si = (struct sockfs_inode *)foo;
>
> - inode_init_once(&ei->vfs_inode);
> + inode_init_once(&si->vfs_inode);
> }
>
> static void init_inodecache(void)
> {
> sock_inode_cachep = kmem_cache_create("sock_inode_cache",
> - sizeof(struct socket_alloc),
> + sizeof(struct sockfs_inode),
> 0,
> (SLAB_HWCACHE_ALIGN |
> SLAB_RECLAIM_ACCOUNT |
> @@ -365,6 +390,7 @@ static void init_inodecache(void)
> static const struct super_operations sockfs_ops = {
> .alloc_inode = sock_alloc_inode,
> .free_inode = sock_free_inode,
> + .evict_inode = sock_evict_inode,
> .statfs = simple_statfs,
> };
>
> @@ -417,9 +443,48 @@ static const struct xattr_handler sockfs_security_xattr_handler = {
> .set = sockfs_security_xattr_set,
> };
>
> +static int sockfs_user_xattr_get(const struct xattr_handler *handler,
> + struct dentry *dentry, struct inode *inode,
> + const char *suffix, void *value, size_t size)
> +{
> + const char *name = xattr_full_name(handler, suffix);
> + struct simple_xattrs *xattrs;
> +
> + xattrs = READ_ONCE(SOCKFS_I(inode)->xattrs);
> + if (!xattrs)
> + return -ENODATA;
> +
> + return simple_xattr_get(xattrs, name, value, size);
> +}
> +
> +static int sockfs_user_xattr_set(const struct xattr_handler *handler,
> + struct mnt_idmap *idmap,
> + struct dentry *dentry, struct inode *inode,
> + const char *suffix, const void *value,
> + size_t size, int flags)
> +{
> + const char *name = xattr_full_name(handler, suffix);
> + struct sockfs_inode *si = SOCKFS_I(inode);
> + struct simple_xattrs *xattrs;
> +
> + xattrs = simple_xattrs_lazy_alloc(&si->xattrs, value, flags);
> + if (IS_ERR_OR_NULL(xattrs))
> + return PTR_ERR(xattrs);
> +
> + return simple_xattr_set_limited(xattrs, &si->xattr_limits,
> + name, value, size, flags);
> +}
> +
> +static const struct xattr_handler sockfs_user_xattr_handler = {
> + .prefix = XATTR_USER_PREFIX,
> + .get = sockfs_user_xattr_get,
> + .set = sockfs_user_xattr_set,
> +};
> +
> static const struct xattr_handler * const sockfs_xattr_handlers[] = {
> &sockfs_xattr_handler,
> &sockfs_security_xattr_handler,
> + &sockfs_user_xattr_handler,
> NULL
> };
>
> @@ -572,26 +637,26 @@ EXPORT_SYMBOL(sockfd_lookup);
> static ssize_t sockfs_listxattr(struct dentry *dentry, char *buffer,
> size_t size)
> {
> - ssize_t len;
> - ssize_t used = 0;
> + struct sockfs_inode *si = SOCKFS_I(d_inode(dentry));
> + ssize_t len, used;
>
> - len = security_inode_listsecurity(d_inode(dentry), buffer, size);
> + len = simple_xattr_list(d_inode(dentry), READ_ONCE(si->xattrs),
> + buffer, size);
> if (len < 0)
> return len;
> - used += len;
> +
> + used = len;
> if (buffer) {
> - if (size < used)
> - return -ERANGE;
> buffer += len;
> + size -= len;
> }
>
> - len = (XATTR_NAME_SOCKPROTONAME_LEN + 1);
> + len = XATTR_NAME_SOCKPROTONAME_LEN + 1;
> used += len;
> if (buffer) {
> - if (size < used)
> + if (size < len)
> return -ERANGE;
> memcpy(buffer, XATTR_NAME_SOCKPROTONAME, len);
> - buffer += len;
> }
>
> return used;
>
> --
> 2.47.3
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2026-02-27 15:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:31 [PATCH 00/14] xattr: rework simple xattrs and support user.* xattrs on sockets Christian Brauner
2026-02-16 13:31 ` [PATCH 01/14] xattr: add rcu_head and rhash_head to struct simple_xattr Christian Brauner
2026-02-27 14:43 ` Jan Kara
2026-02-16 13:31 ` [PATCH 02/14] xattr: add rhashtable-based simple_xattr infrastructure Christian Brauner
2026-02-27 14:43 ` Jan Kara
2026-02-16 13:31 ` [PATCH 03/14] shmem: adapt to rhashtable-based simple_xattrs with lazy allocation Christian Brauner
2026-02-27 14:48 ` Jan Kara
2026-02-16 13:32 ` [PATCH 04/14] kernfs: " Christian Brauner
2026-02-27 15:00 ` Jan Kara
2026-02-16 13:32 ` [PATCH 05/14] pidfs: adapt to rhashtable-based simple_xattrs Christian Brauner
2026-02-27 15:09 ` Jan Kara
2026-02-27 15:16 ` Jan Kara
2026-02-16 13:32 ` [PATCH 06/14] xattr: remove rbtree-based simple_xattr infrastructure Christian Brauner
2026-02-27 15:14 ` Jan Kara
2026-02-16 13:32 ` [PATCH 07/14] xattr: add xattr_permission_error() Christian Brauner
2026-02-27 15:15 ` Jan Kara
2026-02-16 13:32 ` [PATCH 08/14] xattr: switch xattr_permission() to switch statement Christian Brauner
2026-02-27 15:17 ` Jan Kara
2026-02-16 13:32 ` [PATCH 09/14] xattr: move user limits for xattrs to generic infra Christian Brauner
2026-02-21 0:03 ` Darrick J. Wong
2026-02-23 12:13 ` Christian Brauner
2026-02-27 15:20 ` Jan Kara
2026-02-16 13:32 ` [PATCH 10/14] xattr,net: support limited amount of extended attributes on sockfs sockets Christian Brauner
2026-02-27 15:25 ` Jan Kara [this message]
2026-02-16 13:32 ` [PATCH 11/14] xattr: support extended attributes on sockets Christian Brauner
2026-02-27 15:26 ` Jan Kara
2026-02-16 13:32 ` [PATCH 12/14] selftests/xattr: path-based AF_UNIX socket xattr tests Christian Brauner
2026-02-27 15:29 ` Jan Kara
2026-02-16 13:32 ` [PATCH 13/14] selftests/xattr: sockfs " Christian Brauner
2026-02-27 15:30 ` Jan Kara
2026-02-16 13:32 ` [PATCH 14/14] selftests/xattr: test xattrs on various socket families Christian Brauner
2026-02-27 15:32 ` Jan Kara
2026-02-20 0:44 ` [PATCH 00/14] xattr: rework simple xattrs and support user.* xattrs on sockets Darrick J. Wong
2026-02-20 9:23 ` Christian Brauner
2026-02-21 0:14 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nvbbdg5v2o5tzyzhzfpj2cyldsstgxsnwr7qfr36vwsyks7qjv@ey4qw2ut6q7z \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox