From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.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: Wed, 10 Sep 2014 18:36:23 +0200 [thread overview]
Message-ID: <20140910163623.GD16633@rei> (raw)
In-Reply-To: <1095333434.20418604.1410337882836.JavaMail.zimbra@redhat.com>
Hi!
> > I think libcap was compiled with wrong kernel headers and it is a bug in
> > distribution. I had installed these packages all from the default
> > distribution. The value of CAP_LAST_CAP is different.
>
> Someone else reported it already:
> Bug 1046008 - Some capabilities aren't be defined
> https://bugzilla.redhat.com/show_bug.cgi?id=1046008
>
> Patch looks good to me, it makes the bug more visible.
Ok.
--
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
prev parent reply other threads:[~2014-09-10 16:36 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
[not found] ` <1410317916.31685.34.camel@G08JYZSD130126>
[not found] ` <1095333434.20418604.1410337882836.JavaMail.zimbra@redhat.com>
2014-09-10 16:36 ` chrubis [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=20140910163623.GD16633@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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