From: Guangwen Feng <fenggw-fnst@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] containers/netns/netns_sysfs.sh: add kernel version check
Date: Tue, 25 Oct 2016 15:24:13 +0800 [thread overview]
Message-ID: <580F089D.9040401@cn.fujitsu.com> (raw)
In-Reply-To: <1472544117-7584-1-git-send-email-fenggw-fnst@cn.fujitsu.com>
Hi!
Ping, thanks!
Regards,
Guangwen Feng
On 08/30/2016 04:01 PM, Guangwen Feng wrote:
> Sysfs is not mount namespace aware until applying following kernel
> patches in mainline kernel v2.6.35:
>
> a1b3f59 net: Expose all network devices in a namespaces in sysfs
> 417daa1 hotplug: netns aware uevent_helper
> d6523dd net/sysfs: Fix the bitrot in network device kobject namespace support
> 608b4b9 netns: Teach network device kobjects which namespace they are in
>
> Signed-off-by: Guangwen Feng <fenggw-fnst@cn.fujitsu.com>
> Tested-by: Matus Marhefka <mmarhefk@redhat.com>
> ---
> testcases/kernel/containers/netns/netns_sysfs.sh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/testcases/kernel/containers/netns/netns_sysfs.sh b/testcases/kernel/containers/netns/netns_sysfs.sh
> index 290cef8..b3a87ed 100644
> --- a/testcases/kernel/containers/netns/netns_sysfs.sh
> +++ b/testcases/kernel/containers/netns/netns_sysfs.sh
> @@ -29,6 +29,11 @@ DUMMYDEV_HOST="dummy_test0"
> DUMMYDEV="dummy_test1"
> . test.sh
>
> +tst_kvercmp 2 6 35
> +if [ $? -eq 0 ]; then
> + tst_brkm TCONF "sysfs is not mount namespace aware for kernels older than 2.6.35"
> +fi
> +
> setns_check
> if [ $? -eq 32 ]; then
> tst_brkm TCONF "setns not supported"
>
next prev parent reply other threads:[~2016-10-25 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 8:01 [LTP] [PATCH] containers/netns/netns_sysfs.sh: add kernel version check Guangwen Feng
2016-10-25 7:24 ` Guangwen Feng [this message]
2016-10-26 18:17 ` Jiri Jaburek
2016-10-27 7:55 ` Guangwen Feng
2016-10-31 9:28 ` Cyril Hrubis
2016-10-31 14:05 ` Jiri Jaburek
2016-10-31 14:36 ` Cyril Hrubis
2016-11-01 14:30 ` Cyril Hrubis
2016-10-31 9:31 ` Cyril Hrubis
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=580F089D.9040401@cn.fujitsu.com \
--to=fenggw-fnst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.