From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH draft_keys 7/7] keyrings.7: information regarding pre-3.17 limits on root_maxbytes/root_maxkeys
Date: Fri, 25 Nov 2016 04:01:33 +0300 [thread overview]
Message-ID: <20161125010133.GA892@obsidian> (raw)
In-Reply-To: <51643019-bb42-4066-c824-c55b9e668ac6-ASgREoAs3yw@public.gmane.org>
---
man7/keyrings.7 | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 9dac4db..12853e8 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -734,7 +734,8 @@ This is the maximum number of bytes of data that the root user
(UID 0 in the root user namespace)
can hold in the payloads of the keys owned by root.
-The default value in this file is 25,000,000.
+.\"738c5d190f6540539a04baf36ce21d46b5da04bd
+The default value in this file is 25,000,000 (was 20,000 before Linux 3.17).
.\" commit 0b77f5bfb45c13e1e5142374f9d6ca75292252a4
.TP
.IR /proc/sys/kernel/keys/root_maxkeys " (since Linux 2.6.26)"
@@ -743,7 +744,8 @@ This is the maximum number of keys that the root user
(UID 0 in the root user namespace)
may own.
-The default value in this file is 1,000,000.
+.\"738c5d190f6540539a04baf36ce21d46b5da04bd
+The default value in this file is 1,000,000 (was 200 before Linux 3.17).
.PP
With respect to keyrings,
note that each link in a keyring consumes 4 bytes of the keyring payload.
--
2.10.2
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-25 1:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 15:47 Revised keyrings(7) man page for review Michael Kerrisk
[not found] ` <51643019-bb42-4066-c824-c55b9e668ac6-ASgREoAs3yw@public.gmane.org>
2016-11-25 1:00 ` [PATCH draft_keys 0/7] Minor edits Eugene Syromyatnikov
2016-11-25 10:01 ` Michael Kerrisk (man-pages)
2016-11-25 1:00 ` [PATCH draft_keys 1/7] keyctl.2: tfix Eugene Syromyatnikov
2016-11-25 8:35 ` Michael Kerrisk (man-pages)
2016-11-25 1:00 ` [PATCH draft_keys 2/7] keyrings.7: minor clarification rearding storage method used in keyrings Eugene Syromyatnikov
2016-11-25 8:37 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 3/7] keyrings.7: spacing fix Eugene Syromyatnikov
2016-11-25 8:39 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 4/7] keyrings.7: minor clarification regarding decision whether to store big_key in tmpfs or not Eugene Syromyatnikov
2016-11-25 8:40 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 5/7] keyrings.7: tfix Eugene Syromyatnikov
2016-11-25 8:42 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 6/7] " Eugene Syromyatnikov
2016-11-25 8:43 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` Eugene Syromyatnikov [this message]
2016-11-25 8:54 ` [PATCH draft_keys 7/7] keyrings.7: information regarding pre-3.17 limits on root_maxbytes/root_maxkeys Michael Kerrisk (man-pages)
2016-11-26 12:51 ` Revised keyrings(7) man page for review Michael Kerrisk (man-pages)
2016-12-13 11:35 ` David Howells
[not found] ` <25262.1481628931-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 12:43 ` Michael Kerrisk (man-pages)
[not found] ` <9f32a79b-5795-bff4-b741-bf927a525149-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 12:57 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh9JLN4P+Fu+yRCNo96E3VwjYLRquuaf43XRWeuC7gnNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 13:38 ` David Howells
[not found] ` <26913.1481636296-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 13:52 ` Michael Kerrisk (man-pages)
[not found] ` <a5615075-dd39-e206-cbce-385bed72473f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 14:20 ` David Howells
2016-12-14 7:27 ` Michael Kerrisk (man-pages)
2016-12-13 13:31 ` David Howells
2016-12-13 13:41 ` Michael Kerrisk (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=20161125010133.GA892@obsidian \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).