From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] security: add missing PR_CAPBSET_READ/PR_CAPBSET_DROP check
Date: Fri, 21 Jun 2019 10:01:29 +0800 [thread overview]
Message-ID: <5D0C3A79.7090504@cn.fujitsu.com> (raw)
In-Reply-To: <20190620114952.GA31382@dell5510>
> Hi Yang,
>
>> PR_CAPBSET_READ/PR_CAPNSET_DROP was added since linux2.6.25,
>> current ltp detected them in ltp-prctl.m4, but three places
>> missed this check. So add it, fix possible compiler error
>> on some old dirtros without PR_CAPBSET_READ/PR_CAPNSET_DROP flag.
> Thanks for your patch, merged.
>
> BTW these cap files would deserve converting into new API.
Hi Petr
Ok. I will take this as the next plan.
> Kind regards,
> Petr
>
>
>
prev parent reply other threads:[~2019-06-21 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 7:26 [LTP] [PATCH] ltp-cap.m4: add libcap version detection && fix compiler error Yang Xu
2019-05-13 13:14 ` Petr Vorel
2019-05-14 5:24 ` xuyang
2019-05-14 12:01 ` Petr Vorel
2019-05-15 9:01 ` xuyang
2019-05-15 14:37 ` Petr Vorel
2019-05-16 6:44 ` xuyang
2019-05-16 6:52 ` [LTP] [PATCH v2] security: add missing PR_CAPBSET_READ/PR_CAPBSET_DROP check Yang Xu
2019-06-20 11:49 ` Petr Vorel
2019-06-21 2:01 ` Yang Xu [this message]
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=5D0C3A79.7090504@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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