From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: "Alejandro Colomar (mailing lists; readonly)"
<alx.mailinglists@gmail.com>
Cc: <mtk.manpages@gmail.com>, Davidlohr Bueso <dbueso@suse.de>,
<linux-man@vger.kernel.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Robert Kettler <robert.kettler@outlook.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Manfred Spraul <manfred@colorfullife.com>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH] semctl.2: Correct SEM_STAT_ANY description
Date: Tue, 29 Dec 2020 13:09:13 +0800 [thread overview]
Message-ID: <5FEAB9F9.7060307@cn.fujitsu.com> (raw)
In-Reply-To: <746deff0-e919-173b-25f6-34fc465a7ba0@gmail.com>
Hi Alex
I think it is a smple fix. So ping!
Best Regards
Yang Xu
> Hi Yang,
>
> It looks good to me.
> I'll add a few people that might want to comment.
>
> Thanks,
>
> Alex
>
> On 12/22/20 6:55 AM, Yang Xu wrote:
>> 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
>>
>
>
> .
>
next prev parent reply other threads:[~2020-12-29 5:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 5:55 [PATCH] semctl.2: Correct SEM_STAT_ANY description Yang Xu
2020-12-22 11:55 ` Alejandro Colomar (mailing lists; readonly)
2020-12-29 5:09 ` Yang Xu [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=5FEAB9F9.7060307@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=alx.mailinglists@gmail.com \
--cc=dbueso@suse.de \
--cc=ebiederm@xmission.com \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-man@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mhocko@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=robert.kettler@outlook.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 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.