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 1807811 - iptables-restore Segmentation fault under stress testing
Summary: iptables-restore Segmentation fault under stress testing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: 8.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 8.2
Assignee: Phil Sutter
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-27 10:01 UTC by yiche
Modified: 2023-09-15 00:29 UTC (History)
10 users (show)

Fixed In Version: iptables-1.8.4-10.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 17:00:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-39033 0 None None None 2022-05-01 23:38:59 UTC
Red Hat Product Errata RHEA-2020:1889 0 None None None 2020-04-28 17:00:39 UTC

Internal Links: 1942287

Comment 4 Jianwen Ji 2020-03-02 10:56:56 UTC 
Hi Tomas, please help check with devel if this is worth blocker.
Comment 13 Phil Sutter 2020-03-11 15:09:58 UTC 
Upstream commit to backport:

commit c550c81fd373e5753103d20f7902171f0fa79807
Author: Phil Sutter <phil>
Date:   Fri Feb 28 20:32:13 2020 +0100

    nft: cache: Fix nft_release_cache() under stress
    
    iptables-nft-restore calls nft_action(h, NFT_COMPAT_COMMIT) for each
    COMMIT line in input. When restoring a dump containing multiple large
    tables, chances are nft_rebuild_cache() has to run multiple times.
    
    If the above happens, consecutive table contents are added to __cache[1]
    which nft_rebuild_cache() then frees, so next commit attempt accesses
    invalid memory.
    
    Fix this by making nft_release_cache() (called after each successful
    commit) return things into pre-rebuild state again, but keeping the
    fresh cache copy.
    
    Fixes: f6ad231d698c7 ("nft: keep original cache in case of ERESTART")
    Signed-off-by: Phil Sutter <phil>
Comment 15 Aniket Bhat 2020-03-11 15:18:30 UTC 
@Phil, are the other two stack traces I posted above related?
Comment 22 Phil Sutter 2020-03-11 16:49:58 UTC 
Here's a scratch build including the patch from above, it fixes the segfaults we can reproduce: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=27208911
Does that help? Can you try that one?

As said, the stack traces don't look familiar, but this is also a case of memory corruption.
Comment 23 Dan Williams 2020-03-11 17:10:40 UTC 
*** Bug 1812261 has been marked as a duplicate of this bug. ***
Comment 53 errata-xmlrpc 2020-04-28 17:00:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1889
Comment 54 Red Hat Bugzilla 2023-09-15 00:29:56 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.