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: <038984b4-9e95-bc4b-e763-95bf24426f07@intel.com>
Date:   Thu, 22 Jun 2023 13:17:17 -0700
From:   Sohil Mehta <sohil.mehta@...el.com>
To:     Arnd Bergmann <arnd@...db.de>
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 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.

Sohil

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ