public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Günther Noack" <gnoack3000@gmail.com>
Cc: "Mickaël Salaün" <mic@digikod.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] landlock.7: Document Landlock ABI v3 (file truncation; kernel 6.2)
Date: Mon, 6 Mar 2023 13:33:45 +0100	[thread overview]
Message-ID: <192c38ba-efd8-144d-30a2-c81c0eff78bf@gmail.com> (raw)
In-Reply-To: <20230302.2f7c767e1b94@gnoack.org>


[-- Attachment #1.1: Type: text/plain, Size: 2406 bytes --]

On 3/2/23 14:42, Günther Noack wrote:
> Hello Alex!

Hello Günther!

> 
> On Wed, Mar 01, 2023 at 10:21:13PM +0100, Alejandro Colomar wrote:
>> In the subject it's not so important, but for consistency with the
>> language used within the pages, I'd ask you to rewrite it as Linux 6.2
>> (and similarly for patch 1/2).
> 
> Done, sure thing.
> 
> 
>> On 2/28/23 21:52, Günther Noack wrote:
>>> diff --git a/man7/landlock.7 b/man7/landlock.7
>>> index f70a01484..9ddb17ae8 100644
>>> --- a/man7/landlock.7
>>> +++ b/man7/landlock.7
>>> +Note that you might additionally need the
>>
>> "Note that" is usually redundant.
>> See:
>> <https://lore.kernel.org/linux-man/20210729223535.qvyomfqvvahzmu5w@localhost.localdomain/>
>> <https://lore.kernel.org/linux-man/20230105225235.6cjtz6orjzxzvo6v@illithid/>
> 
> Thank you, that is a good observation, the "Kemper notectomy".
> This is very helpful, exactly the kind of review I was hoping for. :)

:)

> 
> How about this rewording:
> 
>   LANDLOCK_ACCESS_FS_WRITE
> 
>     Open a file with write access.
> 
>     When opening files for writing, you will often additionally need
>     the LANDLOCK_ACCESS_FS_TRUNCATE right.  In many cases, these
>     system calls truncate existing files when overwriting them (e.g.
>     creat(2)).

Sounds good.

> 
> This paragraph started with "note that" because it talks about an
> unintuitive side-aspect of the LANDLOCK_ACCESS_FS_WRITE_FILE right.
> 
> I reworded it to make it more clear why that should be relevant to the
> reader (because creat(2) and its open(2) equivalent are used very
> commonly).
> 
> Does that sound better?
> 
> The man page also explains it in more detail in the "Truncating files"
> section further below.
> 
> 
>>> +system call, this can also be done through
>>> +.BR open (2)
>>> +with the flags
>>> +.BR "O_RDONLY | O_TRUNC" .
>>
>> Expressions should go in italics.  See man-pages(7):
>>
>>        Expressions, if not written on a separate indented line, should
>>        be  specified in italics.  Again, the use of nonbreaking spaces
>>        may be appropriate if the expression  is  inlined  with  normal
>>        text.
> 
> Done.
> 
> Thank you for the review!
> –Günther

Cheers,

Alex


-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-03-06 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 20:52 [PATCH v2 1/2] landlock.7: Document Landlock ABI v2 (file reparenting; kernel 5.19) Günther Noack
2023-02-28 20:52 ` [PATCH v2 2/2] landlock.7: Document Landlock ABI v3 (file truncation; kernel 6.2) Günther Noack
2023-03-01 21:21   ` Alejandro Colomar
2023-03-02 13:42     ` Günther Noack
2023-03-06 12:33       ` Alejandro Colomar [this message]
2023-03-01 21:25 ` [PATCH v2 1/2] landlock.7: Document Landlock ABI v2 (file reparenting; kernel 5.19) Alejandro Colomar
2023-03-02 13:52   ` Günther Noack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=192c38ba-efd8-144d-30a2-c81c0eff78bf@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=gnoack3000@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mic@digikod.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox