[LTP] SIGSEGV in faccessat01 and fchmodat01

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Xiuzhe Xiao]

Hi,

Have anyone had these problem?
Is there any requirement for these test? or is anyone can give me a direction, I'll be appreciated

<<<test_output>>>
faccessat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2134).
faccessat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken

<<<test_output>>>
fchmodat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2289).
fchmodat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken


Thanks

Shawnx.

This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20180314/48e84e4a/attachment.html>

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Cyril Hrubis]

Hi!
> Have anyone had these problem?
> Is there any requirement for these test? or is anyone can give me a direction, I'll be appreciated
> 
> <<<test_output>>>
> faccessat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2134).
> faccessat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken
> 
> <<<test_output>>>
> fchmodat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2289).
> fchmodat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken

Can you run the test under gdb and send the backtrace?

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Xiuzhe Xiao]

Hi


Here is the result from gdb

seems like it is getting really deep

(gdb) r
Starting program: /opt/ltp/testcases/bin/fchmodat01

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/arm/strlen.S:33
33              sfi_breg r1, \
(gdb)


Thanks

Shawnx.

________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Thursday, March 15, 2018 4:55:18 AM
To: Xiuzhe Xiao
Cc: ltp@lists.linux.it
Subject: Re: [LTP] SIGSEGV in faccessat01 and fchmodat01

Hi!
> Have anyone had these problem?
> Is there any requirement for these test? or is anyone can give me a direction, I'll be appreciated
>
> <<<test_output>>>
> faccessat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2134).
> faccessat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken
>
> <<<test_output>>>
> fchmodat01    1  TBROK  :  tst_sig.c:233: unexpected signal SIGSEGV(11) received (pid = 2289).
> fchmodat01    2  TBROK  :  tst_sig.c:233: Remaining cases broken

Can you run the test under gdb and send the backtrace?

--
Cyril Hrubis
chrubis@suse.cz
This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20180315/e6b32866/attachment.html>

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Cyril Hrubis]

Hi!
> Here is the result from gdb
> 
> seems like it is getting really deep
> 
> (gdb) r
> Starting program: /opt/ltp/testcases/bin/fchmodat01
> 
> Program received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/arm/strlen.S:33
> 33              sfi_breg r1, \
> (gdb)

What about the backtrace (bt), does it show the call trace?

However this looks rather suspicious, possibly something is wrong with
glibc there.

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Jan Stancek]

----- Original Message -----
> 
> 
> Hi

> Here is the result from gdb
> seems like it is getting really deep
> 
> 
> 
> (gdb) r
> Starting program: /opt/ltp/testcases/bin/fchmodat01
> 
> Program received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/arm/strlen.S:33
> 33 sfi_breg r1, \
> (gdb)

Please send the backtrace as well. Type "bt" and hit enter in gdb
after it crashes.

What distro/kernel/LTP version are you using?

Regards,
Jan

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Xiuzhe Xiao]

(gdb) r
Starting program: /opt/ltp/testcases/bin/fchmodat01

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/arm/strlen.S:33
33              sfi_breg r1, \
(gdb) bt
#0  strlen () at ../sysdeps/arm/strlen.S:33
#1  0x44583cfc in _IO_vfprintf_internal (s=s@entry=0x34030, format=format@entry=0x1c320 "%s/fchmodattest%d.txt", ap=..., ap@entry=...)
    at /usr/src/debug/glibc/2.25-r0/git/stdio-common/vfprintf.c:1637
#2  0x44624e64 in ___vfprintf_chk (fp=fp@entry=0x34030, flag=flag@entry=1, format=0x1c320 "%s/fchmodattest%d.txt",
    format@entry=0x33b64 <testfile2> "/tmp/fchBEt8Uu/fchmodattest816.txt", ap=..., ap@entry=...)
    at /usr/src/debug/glibc/2.25-r0/git/debug/vfprintf_chk.c:33
#3  0x0001383c in vfprintf (__ap=..., __fmt=0x33b64 <testfile2> "/tmp/fchBEt8Uu/fchmodattest816.txt", __stream=0x34030)
    at /usr/include/bits/stdio2.h:127
#4  safe_file_printf (file=file@entry=0x1c2b0 "fchmodat01.c", lineno=lineno@entry=131, cleanup_fn=cleanup_fn@entry=0x121a4 <cleanup>,
    path=path@entry=0x33b64 <testfile2> "/tmp/fchBEt8Uu/fchmodattest816.txt", fmt=fmt@entry=0x1c320 "%s/fchmodattest%d.txt")
    at /usr/src/debug/ltp/20170116-r0/git/lib/safe_file_ops.c:280
#5  0x00012384 in setup () at /usr/src/debug/ltp/20170116-r0/git/testcases/kernel/syscalls/fchmodat/fchmodat01.c:131
#6  0x00011f18 in main (ac=1, av=0xbefffdd4) at /usr/src/debug/ltp/20170116-r0/git/testcases/kernel/syscalls/fchmodat/fchmodat01.c:84
(gdb)

Kernel: 4.0.0-ADI-1.2.0-yocto-standard
LTP Version: 20170116
Distro : Poky (Yocto Project Reference Distro)
DIstro Version: pyro

The kernel was from Analog Device Inc, it is built for the board named ADSP-SC589
Sorry for the lack of information, please tell me if others needed.

Thanks
Shawnx.


________________________________
From: Jan Stancek <jstancek@redhat.com>
Sent: Thursday, March 15, 2018 6:14:49 AM
To: Xiuzhe Xiao
Cc: Cyril Hrubis; ltp@lists.linux.it
Subject: Re: [LTP] SIGSEGV in faccessat01 and fchmodat01


----- Original Message -----
>
>
> Hi

> Here is the result from gdb
> seems like it is getting really deep
>
>
>
> (gdb) r
> Starting program: /opt/ltp/testcases/bin/fchmodat01
>
> Program received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/arm/strlen.S:33
> 33 sfi_breg r1, \
> (gdb)

Please send the backtrace as well. Type "bt" and hit enter in gdb
after it crashes.

What distro/kernel/LTP version are you using?

Regards,
Jan
This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20180315/822d479d/attachment-0001.html>

[LTP] SIGSEGV in faccessat01 and fchmodat01

[Jan Stancek]

----- Original Message -----
> (gdb) r
> Starting program: /opt/ltp/testcases/bin/fchmodat01
> 
> Program received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/arm/strlen.S:33
> 33              sfi_breg r1, \
> (gdb) bt
> #0  strlen () at ../sysdeps/arm/strlen.S:33
> #1  0x44583cfc in _IO_vfprintf_internal (s=s@entry=0x34030,
> format=format@entry=0x1c320 "%s/fchmodattest%d.txt", ap=..., ap@entry=...)
>     at /usr/src/debug/glibc/2.25-r0/git/stdio-common/vfprintf.c:1637
> #2  0x44624e64 in ___vfprintf_chk (fp=fp@entry=0x34030, flag=flag@entry=1,
> format=0x1c320 "%s/fchmodattest%d.txt",
>     format@entry=0x33b64 <testfile2> "/tmp/fchBEt8Uu/fchmodattest816.txt",
>     ap=..., ap@entry=...)
>     at /usr/src/debug/glibc/2.25-r0/git/debug/vfprintf_chk.c:33
> #3  0x0001383c in vfprintf (__ap=..., __fmt=0x33b64 <testfile2>
> "/tmp/fchBEt8Uu/fchmodattest816.txt", __stream=0x34030)
>     at /usr/include/bits/stdio2.h:127
> #4  safe_file_printf (file=file@entry=0x1c2b0 "fchmodat01.c",
> lineno=lineno@entry=131, cleanup_fn=cleanup_fn@entry=0x121a4 <cleanup>,
>     path=path@entry=0x33b64 <testfile2> "/tmp/fchBEt8Uu/fchmodattest816.txt",
>     fmt=fmt@entry=0x1c320 "%s/fchmodattest%d.txt")
>     at /usr/src/debug/ltp/20170116-r0/git/lib/safe_file_ops.c:280
> #5  0x00012384 in setup () at
> /usr/src/debug/ltp/20170116-r0/git/testcases/kernel/syscalls/fchmodat/fchmodat01.c:131
> #6  0x00011f18 in main (ac=1, av=0xbefffdd4) at
> /usr/src/debug/ltp/20170116-r0/git/testcases/kernel/syscalls/fchmodat/fchmodat01.c:84
> (gdb)
> 
> Kernel: 4.0.0-ADI-1.2.0-yocto-standard
> LTP Version: 20170116

Format string for SAFE_FILE_PRINTF was missing in these two tests,
which might explain the crashes.

Can you retry with patch below or LTP version that has it?
  4141bdb441f7 ("faccessat and fchmodat: Fix build warnings")

$ git tag --contains 4141bdb441f7
20170929
20180118

Regards,
Jan

> Distro : Poky (Yocto Project Reference Distro)
> DIstro Version: pyro
> 
> The kernel was from Analog Device Inc, it is built for the board named
> ADSP-SC589
> Sorry for the lack of information, please tell me if others needed.
> 
> Thanks
> Shawnx.
> 
> 
> ________________________________
> From: Jan Stancek <jstancek@redhat.com>
> Sent: Thursday, March 15, 2018 6:14:49 AM
> To: Xiuzhe Xiao
> Cc: Cyril Hrubis; ltp@lists.linux.it
> Subject: Re: [LTP] SIGSEGV in faccessat01 and fchmodat01
> 
> 
> ----- Original Message -----
> >
> >
> > Hi
> 
> > Here is the result from gdb
> > seems like it is getting really deep
> >
> >
> >
> > (gdb) r
> > Starting program: /opt/ltp/testcases/bin/fchmodat01
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > strlen () at ../sysdeps/arm/strlen.S:33
> > 33 sfi_breg r1, \
> > (gdb)
> 
> Please send the backtrace as well. Type "bt" and hit enter in gdb
> after it crashes.
> 
> What distro/kernel/LTP version are you using?
> 
> Regards,
> Jan
> This communication, including any attached documentation, is intended only
> for the person or entity to which it is addressed, and may contain
> confidential, personal, and/or privileged information. Any unauthorized
> disclosure, copying, or taking action on the contents is strictly
> prohibited. If you have received this message in error, please contact us
> immediately so we may correct our records. Please then delete or destroy the
> original transmission and any subsequent reply. Thank you.
>