From: Christoph Hellwig <hch@infradead.org>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Hugh Dickins" <hughd@google.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Rutger van Beusekom" <rutger@reasonable-sourcery.coop>
Subject: Re: [PATCH] shmem: support xattr gnu.* namespace for the Hurd
Date: Sun, 17 May 2026 23:35:08 -0700 [thread overview]
Message-ID: <agqzHDqPIBGuhtFg@infradead.org> (raw)
In-Reply-To: <87se7stpgy.fsf@gnu.org>
On Fri, May 15, 2026 at 09:58:05PM +0200, Janneke Nieuwenhuizen wrote:
> >From d8291d06b67db045033664fb440f59001d7755a1 Mon Sep 17 00:00:00 2001
> From: Janneke Nieuwenhuizen <janneke@gnu.org>
> Date: Fri, 15 May 2026 10:12:30 +0200
> Subject: [PATCH] shmem: support xattr gnu.* namespace for the Hurd
>
> The Hurd gained[0] support for moving the translator and author
> fields out of the inode and into the "gnu.*" xattr namespace.
>
> In anticipation of that, an xattr INDEX was reserved[1]. The Hurd has
> now been brought into compliance[2] with that, and so has ext4[3].
>
> This patch adds support for reading and writing such attributes from
> a Linux tmpfs; you can now do something like
No, making bootstrapping a hobbyist OS is not a good reason to bloat
the Linux kernel. Please patch your bootstrapping code to just use
a user xattr instead.
next prev parent reply other threads:[~2026-05-18 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 19:58 [PATCH] shmem: support xattr gnu.* namespace for the Hurd Janneke Nieuwenhuizen
2026-05-18 3:54 ` Baolin Wang
2026-05-18 6:22 ` Janneke Nieuwenhuizen
2026-05-18 6:35 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-15 19:54 Janneke Nieuwenhuizen
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=agqzHDqPIBGuhtFg@infradead.org \
--to=hch@infradead.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=janneke@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ludo@gnu.org \
--cc=rutger@reasonable-sourcery.coop \
/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