From: Yuan Sun <sunyuan3@huawei.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH V2] userns01: add capability verification
Date: Fri, 3 Jul 2015 17:24:11 +0800 [thread overview]
Message-ID: <559654BB.5050300@huawei.com> (raw)
In-Reply-To: <20150703091815.GA2855@dustball.brq.redhat.com>
Interesting. Log is as follow. I will have a research.
log:
root@ubuntu:/tmp/tt# gcc test.c -lcap
root@ubuntu:/tmp/tt# ls
a.out test.c
root@ubuntu:/tmp/tt# ./a.out
ffffffff ffffffff
ffffffff ffffffff
cap_compare: 0
On 2015/7/3 17:18, Jan Stancek wrote:
> On Fri, Jul 03, 2015 at 05:13:37PM +0800, Yuan Sun wrote:
>> Hi Jan,
>> The following link is unaccessible because HuaWei's network
>> security strategy.
>> Could you please attach the test.c file for me?
>> http://fpaste.org/239445/35909330/
> Was afraid my web email client would mangle it. Attached.
>
> Regards,
> Jan
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-07-03 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 4:22 [LTP] [PATCH V2] userns01: add capability verification Yuan Sun
2015-07-02 14:09 ` Jan Stancek
2015-07-03 3:05 ` Yuan Sun
2015-07-03 7:43 ` Jan Stancek
2015-07-03 9:13 ` Yuan Sun
2015-07-03 9:18 ` Jan Stancek
2015-07-03 9:24 ` Yuan Sun [this message]
2015-07-03 9:32 ` Jan Stancek
2015-07-03 9:37 ` Yuan Sun
2015-07-03 10:27 ` Jan Stancek
2015-07-03 10:51 ` Jan Stancek
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=559654BB.5050300@huawei.com \
--to=sunyuan3@huawei.com \
--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