APAR status
Closed as program error.
Error description
Customer applied Linux patch and found in CLI mmbackup produced stack smash coredump. Reported in: Spectrum scale 5.0.3.1 Linux X86 release 3.10.0-957.21.3.e27.x86_64 gcc-4.8.5-36.el7_6.2.x86_64 Known Impact It writes the following info several times to the screen.. It does not appear to make it into the log files.. ? *** stack smashing detected ***: tsqosnice terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x7f902a881b67] /lib64/libc.so.6(+0x117b22)[0x7f902a881b22] tsqosnice(+0x13e6)[0x5623d48153e6] ======= Memory map: ======== 5623d4814000-5623d4817000 r-xp 00000000 fd:07 25349393?????????????????? /usr/lpp/mmfs/bin/tsqosnice 5623d4a16000-5623d4a17000 r--p 00002000 fd:07 25349393?????????????????? /usr/lpp/mmfs/bin/tsqosnice 5623d4a17000-5623d4a18000 rw-p 00003000 fd:07 25349393?????????????????? /usr/lpp/mmfs/bin/tsqosnice 5623d66ec000-5623d670d000 rw-p 00000000 00:00 0?????? ???????????????????[heap] 7f902a554000-7f902a569000 r-xp 00000000 fd:07 8394017??????????????????? /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f902a569000-7f902a768000 ---p 00015000 fd:07 8394017??????????????????? /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f902a768000-7f902a769000 r--p 00014000 fd:07 8394017??????????????????? /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f902a769000-7f902a76a000 rw-p 00015000 fd:07 8394017??????????????????? /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7f902a76a000-7f902a92c000 r-xp 00000000 fd:07 8395223??????????????????? /usr/lib64/libc-2.17.so 7f902a92c000-7f902ab2c000 ---p 001c2000 fd:07 8395223??????????????????? /usr/lib64/libc-2.17.so 7f902ab2c000-7f902ab30000 r--p 001c2000 fd:07 8395223??????????????????? /usr/lib64/libc-2.17.so 7f902ab30000-7f902ab32000 rw-p 001c6000 fd:07 8395223??????????????????? /usr/lib64/libc-2.17.so 7f902ab32000-7f902ab37000 rw-p 00000000 00:00 0 7f902ab37000-7f902ab4e000 r-xp 00000000 fd:07 8395935??????????????????? /usr/lib64/libpthread-2.17.so 7f902ab4e000-7f902ad4d000 ---p 00017000 fd:07 8395935??????????????????? /usr/lib64/libpthread-2.17.so 7f902ad4d000-7f902ad4e000 r--p 00016000 fd:07 8395935??????????????????? /usr/lib64/libpthread-2.17.so 7f902ad4e000-7f902ad4f000 rw-p 00017000 fd:07 8395935??? ????????????????/usr/lib64/libpthread-2.17.so 7f902ad4f000-7f902ad53000 rw-p 00000000 00:00 0 7f902ad53000-7f902ad67000 r-xp 00000000 fd:07 8580098??????????????????? /usr/lpp/mmfs/lib/libgpfs.so 7f902ad67000-7f902af67000 ---p 00014000 fd:07 8580098?????? ?????????????/usr/lpp/mmfs/lib/libgpfs.so 7f902af67000-7f902af68000 r--p 00014000 fd:07 8580098??????????????????? /usr/lpp/mmfs/lib/libgpfs.so 7f902af68000-7f902af69000 rw-p 00015000 fd:07 8580098??????????????????? /usr/lpp/mmfs/lib/libgpfs.so 7f902af69000-7f902b06a000 r-xp 00000000 fd:07 8395910??????????????????? /usr/lib64/libm-2.17.so 7f902b06a000-7f902b269000 ---p 00101000 fd:07 8395910??????????????????? /usr/lib64/libm-2.17.so 7f902b269000-7f902b26a000 r--p 00100000 fd:07 8395910?????????????????? ?/usr/lib64/libm-2.17.so 7f902b26a000-7f902b26b000 rw-p 00101000 fd:07 8395910??????????????????? /usr/lib64/libm-2.17.so 7f902b26b000-7f902b354000 r-xp 00000000 fd:07 8410348??????????????????? /usr/lib64/libstdc++.so.6.0.19 7f902b354000-7f902b553000 ---p 000e9000 fd:07 8410348??????????????????? /usr/lib64/libstdc++.so.6.0.19 7f902b553000-7f902b55b000 r--p 000e8000 fd:07 8410348??????????????????? /usr/lib64/libstdc++.so.6.0.19 7f902b55b000-7f902b55d000 rw-p 000f0000 fd:07 8410348??????????????????? /usr/lib64/libstdc++.so.6.0.19 7f902b55d000-7f902b572000 rw-p 00000000 00:00 0 7f902b572000-7f902b594000 r-xp 00000000 fd:07 8394498??????????????????? /usr/lib64/ld-2.17.so 7f902b781000-7f902b787000 rw-p 00000000 00:00 0 7f902b790000-7f902b793000 rw-p 00000000 00:00 0 7f902b793000-7f902b794000 r--p 00021000 fd:07 8394498??????????????????? /usr/lib64/ld-2.17.so 7f902b794000-7f902b795000 rw-p 00022000 fd:07 8394498??????????????????? /usr/lib64/ld-2.17.so 7f902b795000-7f902b796000 rw-p 00000000 00:00 0 7fffd2d48000-7fffd2d69000 rw-p 00000000 00:00 0????????????????????????? [stack] 7fffd2d6d000-7fffd2d6f000 r-xp 00000000 00:00 0????????????????????????? [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0????????????????? [vsyscall] .....
Local fix
Problem summary
Problem description: When debugging is enabled for mmbackup, tsqosnice is called to query QOS and then tsqosnice may terminate with a stack smashing error.
Problem conclusion
Benefits of the solution: mmbackup with debugging enabled. Work around: Do not use mmbackup debugging or remove the call to tsqosnice from the mmbackup script. Problem trigger: See problem description. Symptom: Stack smashing error message Platforms affected: Linux Functional Area affected: QOS, mmbackup Customer Impact: Suggested Changed Externals: N/A
Temporary fix
Comments
APAR Information
APAR number
IJ17661
Reported component name
SPEC SCALE STD
Reported component ID
5737F33AP
Reported release
503
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-07-16
Closed date
2019-07-30
Last modified date
2019-07-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SPEC SCALE STD
Fixed component ID
5737F33AP
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"503","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
30 July 2019