[LTP] netns_crtchild

nousi bnousilal@gmail.com
Wed Jul 27 14:42:28 CEST 2016


Thank you, I will migrate to latest ltp release.


On Wed, Jul 27, 2016 at 6:02 PM, Cyril Hrubis <chrubis@suse.cz> wrote:
> Hi!
>> >> netns_parentns.sh 1 TFAIL : Error: unable to create veth pair
>> >> netns_crtchild    1  TFAIL  :  common.c:89: Error while
>
> FYI these testcases were completely rewritten more than year ago mainly
> because they were too messed up to be repaired. You should really try
> with latest released LTP instead.
>
>> >> runninnetns_two_child[14159]: unhandled level 2 translation fault (11)
>> >> at 0x00000000, esr 0x83000006
>> >> g the script
>> >>
>> >> <<<execution_status>>>
>> >> initiation_status="ok"
>> >> pgd = ffffffc0f21cf000
>> >> [00000000] *pgd=000000011c7a3003ed termination_id=1 corefile=no
>> >>                                 cutime=1 cstime=1
>> >> <<<test_end>>>
>> >
>> > As far as I can tell you found a kernel/firmware/hardware bug.
>>
>> Not necessarily -- I think this is just the kernel verbosely
>> reporting that userspace tried to execute from address zero
>> (PC is 0x0, LR looks like a valid value for in the userspace
>> binary, PSTATE indicates EL0, ESR is an instruction-abort fault);
>> it will have sent a SIGSEGV after reporting the register info.
>> That might be because of a kernel/hardware bug but the first
>> thing to look at is what the userspace binary is actually doing
>> (eg run it in a debugger) because the most plausible thing
>> here is "bug in userspace".
>
> Well the binary in which it seems to trigger the trace calls clone() and
> then executes a script via system() and all error paths seems to be
> handled. If you are correct this may as well be glibc or compiler bug
> but that is hard to say without further debugging...
>
> --
> Cyril Hrubis
> chrubis@suse.cz



-- 
Thanks & Regards,
B.Nousilal,


More information about the ltp mailing list