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:   Sat, 10 Aug 2019 08:58:21 -0600
From:   Jonathan Corbet <>
To:     Jonathan Neuschäfer <>
Cc:, "David S. Miller" <>,
        Alexei Starovoitov <>,
        Daniel Borkmann <>,
        Jakub Kicinski <>,
        Jesper Dangaard Brouer <>,
        John Fastabend <>,,,,
Subject: Re: [PATCH] Documentation/networking/af_xdp: Inhibit reference to
 struct socket

On Sat, 10 Aug 2019 14:17:37 +0200
Jonathan Neuschäfer <> wrote:

> With the recent change to auto-detect function names, Sphinx parses
> socket() as a reference to the in-kernel definition of socket. It then
> decides that struct socket is a good match, which was obviously not
> intended in this case, because the text speaks about the syscall with
> the same name.
> Prevent socket() from being misinterpreted by wrapping it in ``inline
> literal`` quotes.
> Signed-off-by: Jonathan Neuschäfer <>

Thanks for looking at that.  The better fix, though, would be to add
socket() to the Skipfuncs array in Documentation/sphinx/
Then it will do the right thing everywhere without the need to add markup
to the RST files.



Powered by blists - more mailing lists