Bug 2123124

Summary: [abrt] rarian-compat: __strcmp_avx2(): rarian-sk-get-cl killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ladar Levison <ladar>
Component: rarianAssignee: Troy Curtis <troy>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: ktsh.tanaka.2020, troy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fc538bdc686d6d0b552fcc5c6d8ae8b95d217ee3
Whiteboard: abrt_hash:5f64728aa17ca9d8770fe4872338bb0af13e6732;
Fixed In Version: rarian-0.8.2-1.fc39 rarian-0.8.2-1.fc36 rarian-0.8.2-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-22 04:01:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Ladar Levison 2022-08-31 18:34:38 UTC 
Version-Release number of selected component:
rarian-compat-0.8.1-30.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.kde.khelpcenter
cmdline:        /usr/bin/rarian-sk-get-cl en scrollkeeper_cl.xml
crash_function: __strcmp_avx2
executable:     /usr/bin/rarian-sk-get-cl
journald_cursor: s=9c62206e08b64f979ae7ef9fbf796a40;i=58915;b=1a163d07f85347ab8c1973cea523d832;m=2e481edf3e;t=5e65c59536266;x=3a8a6fba31d3e95e
kernel:         5.18.16-200.fc36.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:284
 #1 scan_directory at /usr/src/debug/rarian-0.8.1-30.fc36.x86_64/librarian/rarian-main.c:297
 #6 scan_directories at /usr/src/debug/rarian-0.8.1-30.fc36.x86_64/librarian/rarian-main.c:237
Comment 1 Ladar Levison 2022-08-31 18:34:43 UTC 
Created attachment 1908779 [details]
File: backtrace
Comment 2 Ladar Levison 2022-08-31 18:34:45 UTC 
Created attachment 1908780 [details]
File: core_backtrace
Comment 3 Ladar Levison 2022-08-31 18:34:47 UTC 
Created attachment 1908781 [details]
File: cpuinfo
Comment 4 Ladar Levison 2022-08-31 18:34:48 UTC 
Created attachment 1908782 [details]
File: dso_list
Comment 5 Ladar Levison 2022-08-31 18:34:50 UTC 
Created attachment 1908783 [details]
File: environ
Comment 6 Ladar Levison 2022-08-31 18:34:52 UTC 
Created attachment 1908784 [details]
File: exploitable
Comment 7 Ladar Levison 2022-08-31 18:34:53 UTC 
Created attachment 1908785 [details]
File: limits
Comment 8 Ladar Levison 2022-08-31 18:34:56 UTC 
Created attachment 1908786 [details]
File: maps
Comment 9 Ladar Levison 2022-08-31 18:34:58 UTC 
Created attachment 1908787 [details]
File: mountinfo
Comment 10 Ladar Levison 2022-08-31 18:34:59 UTC 
Created attachment 1908788 [details]
File: open_fds
Comment 11 Ladar Levison 2022-08-31 18:35:01 UTC 
Created attachment 1908789 [details]
File: proc_pid_status
Comment 12 Troy Curtis 2022-11-20 00:42:50 UTC 
*** Bug 2080611 has been marked as a duplicate of this bug. ***
Comment 13 Troy Curtis 2022-11-20 00:51:05 UTC 
Looks like use of an invalid pointer when scanning directories:

	  suffix = strrchr (full_name, '.');
	  if (!strcmp (suffix, ".document")) {

If the filename doesn't have a period, such as if it is "README" or similar, then "suffix" is NULL, and boom.

I'm currently trying to figure out if I can find an upstream place to get a patch in.
Comment 14 Fedora Update System 2023-02-22 04:00:00 UTC 
FEDORA-2023-8db973b2bc has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8db973b2bc
Comment 15 Fedora Update System 2023-02-22 04:01:29 UTC 
FEDORA-2023-8db973b2bc has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 16 Fedora Update System 2023-02-24 03:07:17 UTC 
FEDORA-2023-e2438c189b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e2438c189b
Comment 17 Fedora Update System 2023-02-24 03:25:52 UTC 
FEDORA-2023-e643e6375d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e643e6375d
Comment 18 Fedora Update System 2023-02-25 04:35:13 UTC 
FEDORA-2023-e2438c189b has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e2438c189b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e2438c189b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 19 Fedora Update System 2023-02-25 04:59:13 UTC 
FEDORA-2023-e643e6375d has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e643e6375d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e643e6375d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 20 Fedora Update System 2023-03-05 00:53:21 UTC 
FEDORA-2023-e643e6375d has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 21 Fedora Update System 2023-03-05 01:36:45 UTC 
FEDORA-2023-e2438c189b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.