Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Xi Ruoyao" <xry111@xry111.site>, "Huacai Chen" <chenhuacai@kernel.org>
Cc: "Huacai Chen" <chenhuacai@loongson.cn>,
	loongarch@lists.linux.dev,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"Xuefeng Li" <lixuefeng@loongson.cn>, guoren <guoren@kernel.org>,
	"WANG Xuerui" <kernel@xen0n.name>,
	"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
	linux-kernel@vger.kernel.org, loongson-kernel@lists.loongnix.cn,
	stable@vger.kernel.org
Subject: Re: [PATCH] LoongArch: Define __ARCH_WANT_NEW_STAT in unistd.h
Date: Mon, 17 Jun 2024 08:53:15 +0200	[thread overview]
Message-ID: <b783ee7b-1d27-4793-91cc-ff9d3f4f2103@app.fastmail.com> (raw)
In-Reply-To: <c2b1ca127504e519c04a36179ba6c486f2ec0a08.camel@xry111.site>

On Mon, Jun 17, 2024, at 08:45, Xi Ruoyao wrote:
> On Mon, 2024-06-17 at 08:35 +0200, Arnd Bergmann wrote:
>> On Sat, Jun 15, 2024, at 15:12, Xi Ruoyao wrote:
>> > On Sat, 2024-06-15 at 20:12 +0800, Xi Ruoyao wrote:
>> > > 
>> > > [Firefox]:
>> > > https://searchfox.org/mozilla-central/source/security/sandbox/linu
>> > > x/SandboxFilter.cpp#364
>> > 
>> > Just spent some brain cycles to make a quick hack adding a new statx
>> > flag.  Patch attached.
>> > 
>> 
>> Thanks for the prototype. I agree that this is not a good API
>
> What is particular bad with it?  Maybe we can improve before annoying
> VFS guys :).

I can't come up with anything better either, the problem I
see is mainly that the man page has to explain both AT_EMPTY_PATH
and AT_FORCE_EMPTY_PATH, which are very similar for compatibility
reasons only. We would clearly not design a new interface to have
both, but we can't change existing behavior either.

       Arnd

  reply	other threads:[~2024-06-17  6:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 10:01 [PATCH] LoongArch: Define __ARCH_WANT_NEW_STAT in unistd.h Huacai Chen
2024-05-11 12:17 ` Arnd Bergmann
2024-05-11 14:28   ` Huacai Chen
2024-05-11 15:38     ` Arnd Bergmann
2024-05-12  3:11       ` Huacai Chen
2024-05-12  7:52         ` Arnd Bergmann
2024-06-15  8:52           ` Huacai Chen
2024-06-15  8:55             ` Xi Ruoyao
2024-06-15  9:29               ` Huacai Chen
2024-06-15 11:47                 ` Arnd Bergmann
2024-06-15 12:12                   ` Xi Ruoyao
2024-06-15 13:12                     ` Xi Ruoyao
2024-06-17  6:35                       ` Arnd Bergmann
2024-06-17  6:45                         ` Xi Ruoyao
2024-06-17  6:53                           ` Arnd Bergmann [this message]
2024-06-22  7:45                           ` Huacai Chen
2024-06-22 11:04                             ` Xi Ruoyao
2024-05-15  9:30   ` maobibo
2024-05-15 14:25     ` Arnd Bergmann
2024-05-16  2:52       ` maobibo

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=b783ee7b-1d27-4793-91cc-ff9d3f4f2103@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=guoren@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    --cc=loongson-kernel@lists.loongnix.cn \
    --cc=stable@vger.kernel.org \
    --cc=xry111@xry111.site \
    /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