From: Yuan Sun <sunyuan3@huawei.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH V3] container: new testcase pidns32
Date: Tue, 18 Aug 2015 09:08:13 +0800 [thread overview]
Message-ID: <55D2857D.6000909@huawei.com> (raw)
In-Reply-To: <2105335239.10970039.1439818423738.JavaMail.zimbra@redhat.com>
On 2015/8/17 21:33, Jan Stancek wrote:
>
>
>
> ----- Original Message -----
>> From: "Yuan Sun" <sunyuan3@huawei.com>
>> To: jstancek@redhat.com
>> Cc: ltp-list@lists.sourceforge.net
>> Sent: Friday, 14 August, 2015 10:17:24 AM
>> Subject: [PATCH V3] container: new testcase pidns32
>>
>> Kernel imposes a limit of 32 nested levels of pid namespaces.
>>
>> Signed-off-by: Yuan Sun <sunyuan3@huawei.com>
> Hi,
>
> pushed with updated commit message and removed kernel version check.
> Since we expect that 32 levels will work on any kernel, there's
> no need for it now.
Yes, you are right. I agree with you. Thank you.
Yuan
>
> Regards,
> Jan
>
>> ---
>> runtest/containers | 1 +
>> testcases/kernel/containers/pidns/.gitignore | 1 +
>> testcases/kernel/containers/pidns/pidns32.c | 103
>> +++++++++++++++++++++++++++
>> 3 files changed, 105 insertions(+)
>> create mode 100644 testcases/kernel/containers/pidns/pidns32.c
>>
>
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2015-08-18 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:17 [LTP] [PATCH V3] container: new testcase pidns32 Yuan Sun
2015-08-17 13:33 ` Jan Stancek
2015-08-18 1:08 ` Yuan Sun [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=55D2857D.6000909@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