From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ism Hong" <ism.hong@gmail.com>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Christian Brauner" <brauner@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Jeff Xu" <jeffxu@chromium.org>,
"Christian Göttsche" <cgzones@googlemail.com>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips: fix shmctl/semctl/msgctl syscall for o32
Date: Thu, 30 Jan 2025 21:31:52 +0100 [thread overview]
Message-ID: <7afff28d-45e0-4e15-bb37-270856403bf7@app.fastmail.com> (raw)
In-Reply-To: <6d0659c3-fd86-4eab-879f-d9b149462358@gmail.com>
On Thu, Jan 30, 2025, at 15:46, Ism Hong wrote:
> Arnd Bergmann 於 2025/1/28 清晨5:20 寫道:
>
> Thank you for your explanation, and sorry for the late reply due to the
> Chinese New Year.
>
> From your response, I understand that the preferred solution would be
> to modify uClibc to align the behavior of semctl/shmctl/msgctl with
> glibc and musl by adopting a unified feature test macro. If that is the
> case, I will work on preparing a patch for uClibc accordingly.
Yes, that is correct. I think musl doesn't call the separate
syscalls if the architecture provides the old-style socket() syscall,
so it's not affected either way, but glibc needs the revert.
Arnd
prev parent reply other threads:[~2025-01-30 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 11:52 [PATCH] mips: fix shmctl/semctl/msgctl syscall for o32 Ism Hong
2025-01-27 21:20 ` Arnd Bergmann
2025-01-30 8:55 ` Thomas Bogendoerfer
2025-01-30 14:46 ` Ism Hong
2025-01-30 20:31 ` Arnd Bergmann [this message]
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=7afff28d-45e0-4e15-bb37-270856403bf7@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=cgzones@googlemail.com \
--cc=hca@linux.ibm.com \
--cc=ism.hong@gmail.com \
--cc=jeffxu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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