From: chrubis@suse.cz
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] securebits/check_keepcaps.c: Add comments about cap_get_flag may return -1
Date: Tue, 9 Sep 2014 16:40:35 +0200 [thread overview]
Message-ID: <20140909144034.GA6108@rei> (raw)
In-Reply-To: <1407309452.2223.13.camel@G08JYZSD130126>
Hi!
> In RHEL7.0(3.10.0) the value of CAP_LAST_CAP in linux/capability.h is 36, it is
> greater than in the capability.h which is used to create
> libcap.so(libcap-2.22-8) and that value is 34. Then cap_get_flag returns -1, and
> errno is set to EINVAL. Add comments to make this clear.
I'm a bit confused, the sys/capability.h header which is part of libcap
includes the linux/capability.h header which defines the the
CAP_LAST_CAP (at least on my system). So there shouldn't be a
disagreement between these two unless libcap was compiled with wrong
kernel headers which I would call a bug in distribution. Are you sure
that all your packages are up to date?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-09-09 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 7:17 [LTP] [PATCH] securebits/check_keepcaps.c: Add comments about cap_get_flag may return -1 Zeng Linggang
2014-09-09 14:40 ` chrubis [this message]
[not found] ` <1410317916.31685.34.camel@G08JYZSD130126>
[not found] ` <1095333434.20418604.1410337882836.JavaMail.zimbra@redhat.com>
2014-09-10 16:36 ` chrubis
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=20140909144034.GA6108@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.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