public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: tyberry@redhat.com
Cc: linux-man@vger.kernel.org, lgoncalv@redhat.com
Subject: Re: [PATCH] madvise: MADV_SOFT_OFFLINE requests can return -EBUSY
Date: Fri, 1 Nov 2024 14:20:25 +0100	[thread overview]
Message-ID: <20241101132025.t3cfxacvafp6lyav@devuan> (raw)
In-Reply-To: <ZwhJXaNGoA4Y1UNz@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

Hi Tyonnchie,

On Thu, Oct 10, 2024 at 05:41:38PM -0400, tyberry@redhat.com wrote:
> If any page(s) within the add+length range could not be offlined madvise
> will return -EBUSY. This might occur if the page is currently in use or
> locked.
> 
> Signed-off-by: Tyonnchie Berry <tyberry@redhat.com>
> 
> ---
> 
> diff --git a/man/man2/madvise.2 b/man/man2/madvise.2
> index 441edfbc1..13ee7957c 100644
> --- a/man/man2/madvise.2
> +++ b/man/man2/madvise.2
> @@ -702,6 +702,11 @@ The map exists, but the area maps something that isn't a file.
>  .BR MADV_COLLAPSE )
>  Could not charge hugepage to cgroup: cgroup limit exceeded.
>  .TP
> +.B EBUSY
> +(for
> +.B MADV_SOFT_OFFLINE )
> +If any page(s) within the add+length range could not be offlined madvise will return -EBUSY. This might occur if the page is currently in use or locked.

"any pages" includes the possible value 1; there's no need for "()".

Please use semantic newlines.  See man-pages(7).

$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
   Use semantic newlines
     In  the  source of a manual page, new sentences should be started
     on new lines, long sentences should be split into lines at clause
     breaks (commas, semicolons, colons, and so on), and long  clauses
     should be split at phrase boundaries.  This convention, sometimes
     known  as  "semantic newlines", makes it easier to see the effect
     of patches, which often operate at the level of  individual  sen‐
     tences, clauses, or phrases.


Have a lovely day!
Alex

> +.TP
>  .B EFAULT
>  .I advice
>  is
> 

-- 
<https://www.alejandro-colomar.es/>

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

      reply	other threads:[~2024-11-01 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 21:41 [PATCH] madvise: MADV_SOFT_OFFLINE requests can return -EBUSY tyberry
2024-11-01 13:20 ` Alejandro Colomar [this message]

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=20241101132025.t3cfxacvafp6lyav@devuan \
    --to=alx@kernel.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=tyberry@redhat.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