linux-kernel - Re: [PATCH v3 0/6] mips: system call table generation support

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]

Date:   Thu, 6 Dec 2018 17:02:28 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...ux-mips.org>
To:     Joseph Myers <joseph@...esourcery.com>
cc:     Paul Burton <paul.burton@...s.com>,
        Firoz Khan <firoz.khan@...aro.org>,
        "open list:RALINK MIPS ARCHITECTURE" <linux-mips@...ux-mips.org>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <jhogan@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        Arnd Bergmann <arnd@...db.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-Arch <linux-arch@...r.kernel.org>,
        Deepa Dinamani <deepa.kernel@...il.com>,
        Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>,
        libc-alpha@...rceware.org
Subject: Re: [PATCH v3 0/6] mips: system call table generation support

On Thu, 6 Dec 2018, Joseph Myers wrote:

> >  I believe this file is used by the glibc build process to retrieve 
> > syscall numbers for glibc's own use as well for <sys/syscall.h>.  Has the 
> > change been verified not to break this process?
> > 
> >  Cc-ing <libc-alpha@...rceware.org> for information and possible further 
> > input.
> 
> I'm not sure what "this file" is.  The glibc build uses the installed 
> <asm/unistd.h> (the results of #including it, not any other kind of 
> processing the file).

 So how are `SYS_<name>' macros generated that land in <bits/syscall.h>?

  Maciej