Bug 2054825 - sssd_be segfault at 0 ip 00007f16b5fcab7e sp 00007fffc1cc0988 error 4 in libc-2.28.so[7f16b5e72000+1bc000]
Summary: sssd_be segfault at 0 ip 00007f16b5fcab7e sp 00007fffc1cc0988 error 4 in libc...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.5
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: shridhar
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-15 19:05 UTC by Jeremy Absher
Modified: 2023-08-14 08:27 UTC (History)
14 users (show)

Fixed In Version: sssd-2.9.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 6659 0 None open sssd_be segfault at 0 ip 00007f16b5fcab7e sp 00007fffc1cc0988 error 4 in libc-2.28.so[7f16b5e72000+1bc000] 2023-04-05 14:12:26 UTC
Github SSSD sssd pull 6660 0 None open fail_over: protect against a segmentation fault 2023-04-05 22:14:13 UTC
Red Hat Issue Tracker NMT-7 0 None None None 2023-01-19 11:22:11 UTC
Red Hat Issue Tracker RHELPLAN-112386 0 None None None 2022-02-15 19:19:38 UTC
Red Hat Issue Tracker SSSD-4557 0 None None None 2022-04-07 13:26:02 UTC

Comment 1 Alexey Tikhonov 2022-02-15 20:02:56 UTC 
(In reply to Jeremy Absher from comment #0)
> 
> How reproducible:
> Always.  

Great. Please enable 'debug_level = 9', wait for a crash and attach sssd_$domain.log (as a private comment).

> 
> #0  __strcasecmp_l_sse42 () at
> ../sysdeps/x86_64/multiarch/strcmp-sse42.S:1648
> No locals.
> #1  0x000055d76e45d064 in be_resolve_server_process (
>     subreq=subreq@entry=0x55d77047da40, state=state@entry=0x55d770434f50,
>     new_subreq=new_subreq@entry=0x7ffd94d0b0c0)
>     at src/providers/data_provider_fo.c:682
>         ret = 0
>         srv_status_change = 0
>         callback = <optimized out>
>         srvname = <optimized out>
>         __FUNCTION__ = "be_resolve_server_process"
> #2  0x000055d76e45d2d0 in be_resolve_server_done (subreq=0x55d77047da40)
>     at src/providers/data_provider_fo.c:555
>         new_subreq = 0x7f4097f42dd0 <tevent_req_destructor>
>         req = 0x55d770434d90
>         state = 0x55d770434f50
>         timeout = 31
>         ret = <optimized out>
>         __FUNCTION__ = "be_resolve_server_done"


Most probably duplicate of bz 1884912 (and bz 1773488)
Comment 7 Scott Dowdle 2022-06-02 21:41:58 UTC 
I have this also in EL9 (with AlmaLinux 9)
Comment 10 Alexey Tikhonov 2022-08-16 15:36:34 UTC 
JFTR: another crash bug under `be_resolve_server_done()`: bz 2052918
Comment 11 Abhijit Roy 2022-08-30 16:28:42 UTC 
(In reply to Alexey Tikhonov from comment #10)
> JFTR: another crash bug under `be_resolve_server_done()`: bz 2052918

Hi Sumit/Alexey,

On case: 03292814 cus is not able to see any segfaults after adding `ad_enabled_domains`
Comment 13 Alexey Tikhonov 2022-09-16 15:01:18 UTC 
bz 2052918 and https://github.com/SSSD/sssd/issues/6007 might be relevant (or not).
Comment 16 Alexey Tikhonov 2023-01-20 15:34:54 UTC 
Also see https://bugzilla.redhat.com/show_bug.cgi?id=2035625#c6
Comment 22 Alexey Tikhonov 2023-04-05 16:39:20 UTC 
Upstream PR: https://github.com/SSSD/sssd/pull/6660
Comment 23 Alexey Tikhonov 2023-06-06 12:27:36 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/6660

* `master`
    * 8a8869994745429b3f5535a5d0b91f1d0b2fa723 - fail_over: protect against a segmentation fault
* `sssd-2-9`
    * f63a54c3d89866949810d5bcdb09bf2edd3ced02 - fail_over: protect against a segmentation fault
Note You need to log in before you can comment on or make changes to this bug.