From: Alejandro Colomar <alx.manpages@gmail.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Yang Xu <xuyang2018.jy@cn.fujitsu.com>,
linux-man@vger.kernel.org,
Manfred Spraul <manfred@colorfullife.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: [PATCH] semctl.2: Correct SEM_STAT_ANY description
Date: Tue, 29 Dec 2020 12:03:11 +0100 [thread overview]
Message-ID: <20201229110309.7774-1-alx.manpages@gmail.com> (raw)
From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
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>
Acked-by: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
Hi Michael,
Here's a recent patch from Yang Xu.
Cheers,
Alex
man2/semctl.2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man2/semctl.2 b/man2/semctl.2
index ed5e79efd..e562d0bc4 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
base-commit: c55f66855eccfcd92b35fe7b13a326121f2ee0fd
--
2.29.2
next reply other threads:[~2020-12-29 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 11:03 Alejandro Colomar [this message]
2021-01-07 13:05 ` [PATCH] semctl.2: Correct SEM_STAT_ANY description Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2020-12-22 5:55 Yang Xu
2020-12-22 11:55 ` 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
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=20201229110309.7774-1-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mtk.manpages@gmail.com \
--cc=xuyang2018.jy@cn.fujitsu.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).