"ioctl" test failed on "linux-linaro-lsk-highbank"

[Botao]

For "ltp" test suite on "linux-linaro-lsk-highbank", "ioctl" test failed with following information:

https://validation.linaro.org/dashboard/attachment/735212/view#L2606

ioctl03 1 TBROK : opening /dev/net/tun failed: errno=ENOENT(2): No such file or directory
ioctl03 2 TBROK : Remaining cases broken

The hardware pack and rootfs are:

http://snapshots.linaro.org/kernel-hwpack/linux-linaro-stable-lsk-highbank/244/hwpack_linaro-highbank_20140331-2311_b244_armhf_supported.tar.gz

http://snapshots.linaro.org/ubuntu/images/developer/650/linaro-saucy-developer-20140325-650.tar.gz

[Naresh Kamboju (naresh-kamboju)]

As per the initial investigation the root cause of the failure could be because of Kernel config CONFIG_TUN not enabled.
# CONFIG_TUN is not set

config-3.10.35-linaro-highbank attached.

[Alex Shi (alex-shi)]

Naresh,
Do you mean with the CONFIG_TUN opening, the case passed? If so, it should not be a bug.

[Naresh Kamboju (naresh-kamboju)]

Alex,
I do not have highbank hardware with me and not tested locally.
on LAVA also i did not tested by opening CONFIG_TUN=y.

The Question here is Does highbank kernel config need Network features like CONFIG_TUN=y ?
What is the expected kernel config for highbank ? What is missing in current build? which is causing LTP test case ioctl03 reporting failure.

[Botao (botao-sun)]

@Alex, 2 possibilities:

1. If the current Kernel config for highbank is working as expected, as say NOT enable "CONFIG_TUN", then corresponding test cases should be removed - "ioctl03 1" & "ioctl03 2";

2. If we do need support "CONFIG_TUN" on LSK highbank, then current Kernel configuration needs to be updated, and those 2 test cases should be kept.

So as Naresh appended, what is the expected Kernel config for LSK highbank?

[Mark Brown (broonie)]

What is the test case actually supposed to be testing?

[Naresh Kamboju (naresh-kamboju)]

Here is the test case:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioctl/ioctl03.c

1. test case opens a file "/dev/net/tun"
2. tests whether all the valid IFF flags are returned properly by implementation of TUNGETFEATURES ioctl.

In the current case test failed at step 1. test do not found /dev/net/tun

[Alex Shi (alex-shi)]

1, I add the CONFIG_TUN to highbank.conf and push it to -test branch for testing.
2, only arndale has this configure, omap4/express have no this. Are they good for this case?

[Mark Brown (broonie)]

This isn't related to hardware at all, if we're going to add it it should be in one of the generic fragments like distribution.conf.

[Mark Brown (broonie)]

I've (hopefully) added CONFIG_TUN to distribution.conf so hopefully it'll be enabled for all the builds now.

[Naresh Kamboju (naresh-kamboju)]

After enabling CONFIG_TUN=y
ioctl03 test case stopped reporting failure.

ioctl03 0 TINFO : Available features are: 0x7103
ioctl03 0 TINFO : TUN 0x1
ioctl03 0 TINFO : TAP 0x2
ioctl03 0 TINFO : NO_PI 0x1000
ioctl03 0 TINFO : ONE_QUEUE 0x2000
ioctl03 0 TINFO : VNET_HDR 0x4000
ioctl03 0 TINFO : MULTI_QUEUE 0x100

LAVA test output:
https://validation.linaro.org/scheduler/job/119780/log_file#L_81_12498