linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: <mtk.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>, Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Subject: [PATCH] semctl.2: Correct SEM_STAT_ANY description
Date: Tue, 22 Dec 2020 13:55:43 +0800	[thread overview]
Message-ID: <1608616543-21436-1-git-send-email-xuyang2018.jy@cn.fujitsu.com> (raw)

Since kernel commit a280d6dc77eb ("ipc/sem: introduce semctl(SEM_STAT_ANY)"),
it only skips read access check when using SEM_STAT_ANY command. And it should
use the semid_ds struct instead of seminfo struct. Fix this.

Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
---
 man2/semctl.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man2/semctl.2 b/man2/semctl.2
index dd3fb077b..a7462c5cc 100644
--- a/man2/semctl.2
+++ b/man2/semctl.2
@@ -297,8 +297,8 @@ all semaphore sets on the system.
 .TP
 .BR SEM_STAT_ANY " (Linux-specific, since Linux 4.17)"
 Return a
-.I seminfo
-structure containing the same information as for
+.I semid_ds
+structure as for
 .BR SEM_STAT .
 However,
 .I sem_perm.mode
-- 
2.23.0




             reply	other threads:[~2020-12-22  5:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  5:55 Yang Xu [this message]
2020-12-22 11:55 ` [PATCH] semctl.2: Correct SEM_STAT_ANY description Alejandro Colomar (mailing lists; readonly)
2020-12-29  5:09   ` Yang Xu
2020-12-29 10:38   ` Manfred Spraul
2020-12-29 11:12     ` Alejandro Colomar (mailing lists; readonly)
2020-12-30  2:03     ` Yang Xu
2020-12-30 11:20       ` Manfred Spraul
2020-12-30 13:35         ` Michael Kerrisk (man-pages)
2020-12-30 14:33           ` Manfred Spraul
2020-12-30 15:51             ` Michael Kerrisk (man-pages)
2021-01-07  6:54               ` Yang Xu
2020-12-29 11:03 Alejandro Colomar
2021-01-07 13:05 ` 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=1608616543-21436-1-git-send-email-xuyang2018.jy@cn.fujitsu.com \
    --to=xuyang2018.jy@cn.fujitsu.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).