linux-kernel - Re: [PATCH] syscalls: Remove file path comments from headers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <0344615b-5148-4641-a99c-ef75a387b261@app.fastmail.com>
Date:   Fri, 23 Jun 2023 10:06:51 +0200
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Sohil Mehta" <sohil.mehta@...el.com>
Cc:     linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
        Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH] syscalls: Remove file path comments from headers

On Thu, Jun 22, 2023, at 22:17, Sohil Mehta wrote:
> On 6/22/2023 8:10 AM, Arnd Bergmann wrote:
>> Applied to the asm-generic tree, thanks!
>> 
>
> Great, thanks for the quick response.
>
> While going through the comments, I was wondering if we have a
> definition of what constitutes a deprecated syscall vs an obsolete one?
>
> For deprecated we have some information saying:
>> /*
>>  * Deprecated system calls which are still defined in
>>  * include/uapi/asm-generic/unistd.h and wanted by >= 1 arch
>>  */
>
> But, I couldn't find anything for obsolete system calls.

I don't think we've ever defined the two terms properly,
I would assume they are used interchangeably here. If we wanted
a definition, 'obsolete' could mean syscalls that are no longer
used by current software while 'deprecated' are those that
are still called by glibc and others on the architectures that
provide them but are emulated through modern variants on other
architectures. Without any documentation on the topic, or a
definite list, other interpretations are equally possible.

     Arnd