All of lore.kernel.org
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 1/2] memfd_secret.2: mention that it inhibits hibernation
Date: Sun, 23 Jan 2022 13:34:28 +0100	[thread overview]
Message-ID: <23c18a1fd4f31e59f282a90d2a2437e6355849f1.1642941187.git.nabijaczleweli@nabijaczleweli.xyz> (raw)

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

Ref: https://lore.kernel.org/all/20210518072034.31572-6-rppt@kernel.org/
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
---
 man2/memfd_secret.2 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/man2/memfd_secret.2 b/man2/memfd_secret.2
index f3380818e..e9fc8aaa0 100644
--- a/man2/memfd_secret.2
+++ b/man2/memfd_secret.2
@@ -101,7 +101,10 @@ unless the close-on-exec flag has been set.
 .PP
 The memory region is locked into memory in the same way as with
 .BR mlock (2),
-so that it will never be written into swap.
+so that it will never be written into swap,
+and hibernation is inhibited for as long as any
+.BR memfd_secret ()
+descriptions exist.
 However the implementation of
 .BR memfd_secret ()
 will not try to populate the whole range during the
-- 
2.30.2


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

             reply	other threads:[~2022-01-23 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 12:34 наб [this message]
2022-01-23 12:36 ` [PATCH 2/2] memfd_secret.2: mention ENOSYS is also returned when secretmem_enable=0 наб

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=23c18a1fd4f31e59f282a90d2a2437e6355849f1.1642941187.git.nabijaczleweli@nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.