RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1794332 - [abrt] [faf] wpa_supplicant: wpas_p2p_long_listen_timeout(): /usr/sbin/wpa_supplicant killed by 11
Summary: [abrt] [faf] wpa_supplicant: wpas_p2p_long_listen_timeout(): /usr/sbin/wpa_su...
Keywords:
Status: CLOSED DUPLICATE of bug 1693684
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: wpa_supplicant
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Davide Caratti
QA Contact: Ken Benoit
URL: https://faf.lab.eng.brq.redhat.com/fa...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-23 10:24 UTC by Vladimir Benes
Modified: 2020-10-15 15:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-15 15:46:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vladimir Benes 2020-01-23 10:24:39 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/40cb8affb459371aa60b86dd6f0f0f9ddc7d76d6/

Comment 1 Davide Caratti 2020-06-17 08:20:45 UTC
static void wpas_p2p_long_listen_timeout(void *eloop_ctx, void *timeout_ctx)
{
        struct wpa_supplicant *wpa_s = eloop_ctx;
        wpa_s->global->p2p_long_listen = 0;
}


A SIGSEGV here might be due to NULL 'wpa_'s or NULL 'global', and wpa_s might be NULL in case the tested binary does not have yet the fix for bz1752780. Can you confirm that the problem is still present in wpa_supplicant-2.9-2 ?

Comment 3 Davide Caratti 2020-07-02 12:47:02 UTC
no need to fix this urgently, repurposing for 8.4

Comment 6 Davide Caratti 2020-10-15 15:46:31 UTC
(In reply to Davide Caratti from comment #1)
> static void wpas_p2p_long_listen_timeout(void *eloop_ctx, void *timeout_ctx)
> {
>         struct wpa_supplicant *wpa_s = eloop_ctx;
>         wpa_s->global->p2p_long_listen = 0;
> }
> 
> 
> A SIGSEGV here might be due to NULL 'wpa_'s or NULL 'global', and wpa_s
> might be NULL in case the tested binary does not have yet the fix for
> bz1752780. Can you confirm that the problem is still present in
> wpa_supplicant-2.9-2 ?


not sure if the report in comment #0 affects versions earlier than internal snapshot #3. Anyway, I think it's worth retesting after the fix for bz1693684, and see if the segfault happens again. Please re-open in case you find the issue again on binaries candidate for 8.4.

thanks!
-- 
davide

*** This bug has been marked as a duplicate of bug 1693684 ***


Note You need to log in before you can comment on or make changes to this bug.