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  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, 12 Apr 2018 20:20:12 +0200
From:   "Michael Kerrisk (man-pages)" <>
To:     Jan Kara <>
Cc:     Dan Williams <>,
        Ross Zwisler <>,
        Christoph Hellwig <>,
        "" <>,, Linux-MM <>,
        Linux API <>,
        Ext4 Developers List <>,
        xfs <>,
        "Darrick J . Wong" <>
Subject: Re: [PATCH] mmap.2: Add description of MAP_SHARED_VALIDATE and MAP_SYNC

Jan, Ross.

On 12 April 2018 at 16:22, Jan Kara <> wrote:
> Hello Michael!
> On Thu 12-04-18 15:00:49, Michael Kerrisk (man-pages) wrote:
>> Hello Jan,
>> I have applied your patch, and tweaked the text a little, and pushed
>> the result to the git repo.
> Thanks!
>> > +type will silently ignore this flag.
>> > +This flag is supported only for files supporting DAX (direct mapping of persistent
>> > +memory). For other files, creating mapping with this flag results in
>> > +error. Shared file mappings with this flag provide the guarantee that while
>> > +some memory is writeably mapped in the address space of the process, it will
>> > +be visible in the same file at the same offset even after the system crashes or
>> > +is rebooted. This allows users of such mappings to make data modifications
>> > +persistent in a more efficient way using appropriate CPU instructions.
>> It feels like there's a word missing/unclear wording in the previous
>> line, before "using". Without that word, the sentence feels a bit
>> ambiguous.
>> Should it be:
>> persistent in a more efficient way *through the use of* appropriate
>> CPU instructions.
>> or:
>> persistent in a more efficient way *than using* appropriate CPU instructions.
>> ?
>> Is suspect the first is correct, but need to check.
> Yes, the first is correct.

Thanks for both checking that phrasing. In the end I decided to reword
the sentence a bot more substantially:

              In  conjunction  with  the  use of appropriate CPU
              instructions, this provides users of such mappings
              with a more efficient way of making data modifica‚Äź
              tions persistent.



Michael Kerrisk
Linux man-pages maintainer;
Linux/UNIX System Programming Training:

Powered by blists - more mailing lists