From: Linus Torvalds <[email protected]>
To: Xi Ruoyao <[email protected]>
Cc: Christian Brauner <[email protected]>,
[email protected],
"Andreas K. Huettel" <[email protected]>,
Arnd Bergmann <[email protected]>,
Huacai Chen <[email protected]>,
Mateusz Guzik <[email protected]>,
Alexander Viro <[email protected]>,
Jan Kara <[email protected]>,
[email protected], [email protected],
[email protected], Jens Axboe <[email protected]>,
[email protected]
Subject: Re: [PATCH 2/2] vfs: support statx(..., NULL, AT_EMPTY_PATH, ...)
Date: Wed, 3 Jul 2024 12:05:04 -0700 [thread overview]
Message-ID: <CAHk-=wiJh1egNXJN7AsqpE76D4LCkUQTj+RboO7O=3AFeLGesw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Wed, 3 Jul 2024 at 11:48, Xi Ruoyao <[email protected]> wrote:
>
> Fortunately LoongArch ILP32 ABI is not finalized yet (there's no 32-bit
> kernel and 64-bit kernel does not support 32-bit userspace yet) so we
> can still make it happen to use struct statx as (userspace) struct
> stat...
Oh, no problem then. If there are no existing binaries, then yes,
please do that,
It avoids the compat issues too.
I think 'struct statx' is a horrid bloated thing (clearing those extra
"spare" words is a pain, and yes, the user copy for _regular_ 'stat()'
already shows up in profiles), but for some new 32-bit platform it's
definitely worth the pain just to avoid the compat code or new
structure definitions.
Linus
next prev parent reply other threads:[~2024-07-03 19:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 11:00 [PATCH 0/2] statx NULL path support Mateusz Guzik
2024-06-25 11:00 ` [PATCH 1/2] vfs: add CLASS fd_raw Mateusz Guzik
2024-06-25 12:22 ` Xi Ruoyao
2024-06-25 13:13 ` Mateusz Guzik
2024-06-25 11:00 ` [PATCH 2/2] vfs: support statx(..., NULL, AT_EMPTY_PATH, ...) Mateusz Guzik
2024-06-25 13:24 ` Xi Ruoyao
2024-06-25 13:28 ` Xi Ruoyao
2024-06-25 13:28 ` Mateusz Guzik
2024-06-25 14:09 ` Huacai Chen
2024-06-25 14:58 ` Xi Ruoyao
2024-06-30 1:40 ` Huacai Chen
2024-06-30 2:39 ` Xi Ruoyao
2024-06-30 13:18 ` Huacai Chen
2024-07-01 11:59 ` Arnd Bergmann
2024-07-02 15:36 ` Huacai Chen
2024-07-02 17:06 ` Arnd Bergmann
2024-07-03 4:30 ` Huacai Chen
2024-07-03 8:45 ` Christian Brauner
2024-07-03 9:35 ` Huacai Chen
2024-07-03 10:07 ` Xi Ruoyao
2024-07-03 16:31 ` Linus Torvalds
2024-07-03 16:54 ` Xi Ruoyao
2024-07-03 17:09 ` Linus Torvalds
2024-07-03 17:30 ` Xi Ruoyao
2024-07-03 17:40 ` Linus Torvalds
2024-07-03 17:54 ` Linus Torvalds
2024-07-03 18:14 ` Christian Brauner
2024-07-03 18:39 ` Christian Brauner
2024-07-03 19:00 ` Linus Torvalds
2024-07-03 19:18 ` Linus Torvalds
2024-07-03 18:48 ` Xi Ruoyao
2024-07-03 19:05 ` Linus Torvalds [this message]
2024-07-03 19:33 ` Christian Brauner
2024-07-03 19:52 ` Linus Torvalds
2024-07-03 18:44 ` Arnd Bergmann
2024-07-03 19:55 ` Christian Brauner
2024-07-03 17:11 ` Xi Ruoyao
2024-07-04 2:38 ` Huacai Chen
2024-07-04 3:23 ` Xi Ruoyao
2024-07-04 4:14 ` Xi Ruoyao
2024-07-04 5:55 ` Florian Weimer
2024-07-04 6:02 ` Xi Ruoyao
2024-07-01 4:38 ` [PATCH 0/2] statx NULL path support Christoph Hellwig
2024-07-01 6:46 ` Xi Ruoyao
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='CAHk-=wiJh1egNXJN7AsqpE76D4LCkUQTj+RboO7O=3AFeLGesw@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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