linux-kernel - Re: [PATCH 22/24] membarrier.2: Note that glibc does not provide a wrapper

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: <20200928125227.yr2ugl23ib6mid76@localhost.localdomain>
Date:   Mon, 28 Sep 2020 22:52:29 +1000
From:   "G. Branden Robinson" <g.branden.robinson@...il.com>
To:     Alejandro Colomar <colomar.6.4.3@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-man@...r.kernel.org,
        mtk.manpages@...il.com
Subject: Re: [PATCH 22/24] membarrier.2: Note that glibc does not provide a
 wrapper

At 2020-09-27T22:05:14+0200, Alejandro Colomar wrote:
> Hi Branden,
> 
> * G. Branden Robinson via linux-man:
> 
> 1)
> 
> > .EX
> > .B int fstat(int \c
> > .IB fd , \~\c
> > .B struct stat *\c
> > .IB statbuf );
> > .EE
> 
> 2)
> 
> > .EX
> > .BI "int fstat(int " fd ", struct stat *" statbuf );
> > .EE
> 
> 3)
> 
> > .EX
> > .BI "int fstat(int\~" fd ", struct stat *" statbuf );
> > .EE
> 
> I'd say number 2 is best.  Rationale: grep :)
> I agree it's visually somewhat harder, but grepping is way easier.

I don't see how (2) is any tougher to grep than (3)...?

If I'm grepping, I'm usually concerned with things like
variable/function names and not with punctuation, so if I were grepping
for the above function signature I'd probably write:

$ grep 'fstat.*fd.*statbuf' man2/*

...which would catch either of the above just fine.

Am I missing something?

Regards,
Branden

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)