public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, Topi Miettinen <toiwoton@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-mm@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] mmap.2: ENOMEM possible when exceeding VA space
Date: Mon, 22 Nov 2021 18:16:56 +0100	[thread overview]
Message-ID: <e4c2be0f-d9c6-82b6-08ea-94aa09b2ae99@gmail.com> (raw)
In-Reply-To: <20211122161524.cedefwd2t4jck5ua@jwilk.net>

Hi Jakub,

On 11/22/21 17:15, Jakub Wilk wrote:
> * Topi Miettinen <toiwoton@gmail.com>, 2021-11-11, 20:04:
>> +.B ENOMEM
>> +We don't like
>> +.IR addr ,
>> +because it exceeds the virtual address space of the CPU.
>> +.TP
> 
> Who is "we"?

I was going to ask the same, but that page already describes other 
errors like that.  If only for consistency, and avoiding a complete 
rewrite of that ERRORS section, I applied the patch as is.

But yes, "we" doesn't sound like very technical.  Maybe we should fix this.

> 
> FWIW, failing with ENOMEM in this case may seem weird, but this is what 
> POSIX prescribes.
> 

Thanks,
Alex


-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-11-22 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 18:04 [PATCH] mmap.2: ENOMEM possible when exceeding VA space Topi Miettinen
2021-11-22 16:15 ` Jakub Wilk
2021-11-22 17:16   ` Alejandro Colomar (man-pages) [this message]
2021-11-22 17:00 ` Alejandro Colomar (man-pages)

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=e4c2be0f-d9c6-82b6-08ea-94aa09b2ae99@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=toiwoton@gmail.com \
    /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