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:   Sun, 7 Apr 2019 21:02:38 +0800
From:   "Li, Aubrey" <>
To:     Alexey Dobriyan <>,
        Thomas Gleixner <>
Cc:, Peter Zijlstra <>,
        "H. Peter Anvin" <>,,,,,,
        LKML <>,
        Linux API <>,
        Andrew Morton <>
Subject: Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture
 specific output

On 2019/4/7 5:41, Alexey Dobriyan wrote:
> On Fri, Apr 05, 2019 at 09:32:35PM +0200, Thomas Gleixner wrote:
>>> +/* Add support for architecture specific output in /proc/pid/status */
>>> +extern void arch_proc_pid_status(struct seq_file *m, struct task_struct *task);
>      ^^^^^^
> Unnecessary extern.
The linkage is default extern, but with this functions and variables
can be treated the same way.

Is it mandatory not to use it explicitly? ./script/ did
not report this.


Powered by blists - more mailing lists