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 1805611 - xtables-monitor crash when target TRACE rule get matched
Summary: xtables-monitor crash when target TRACE rule get matched
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: 8.2
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On:
Blocks: 1806606
TreeView+ depends on / blocked
 
Reported: 2020-02-21 07:48 UTC by yiche
Modified: 2020-04-28 17:00 UTC (History)
3 users (show)

Fixed In Version: iptables-1.8.4-9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1806606 (view as bug list)
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 Product Errata RHEA-2020:1889 0 None None None 2020-04-28 17:00:39 UTC

Comment 1 Phil Sutter 2020-02-24 12:24:26 UTC
Fixed upstream, commits to backport:

commit 1639b8ba5105542c73e0e1c35e70f245dab89d81
Author: Phil Sutter <phil>
Date:   Fri Feb 21 13:18:32 2020 +0100

    xtables: Align effect of -4/-6 options with legacy
    
    Legacy iptables doesn't accept -4 or -6 if they don't match the
    symlink's native family. The only exception to that is iptables-restore
    which simply ignores the lines introduced by non-matching options, which
    is useful to create combined dump files for feeding into both
    iptables-restore and ip6tables-restore.
    
    Signed-off-by: Phil Sutter <phil>

commit 0f40a8bc49d3f7b815336199931a82f919f37c4e
Author: Phil Sutter <phil>
Date:   Fri Feb 21 13:29:05 2020 +0100

    xtables: Drop -4 and -6 support from xtables-{save,restore}
    
    Legacy tools don't support those options, either.
    
    Signed-off-by: Phil Sutter <phil>

commit d0446ab11182f6ca2adc486a124895f09a220c6e
Author: Phil Sutter <phil>
Date:   Fri Feb 21 14:55:52 2020 +0100

    xtables: Review nft_init()
    
    Move common code into nft_init(), such as:
    
    * initial zeroing nft_handle fields
    * family ops lookup and assignment to 'ops' field
    * setting of 'family' field
    
    This requires minor adjustments in xtables_restore_main() so extra field
    initialization doesn't happen before nft_init() call.
    
    As a side-effect, this fixes segfaulting xtables-monitor binary when
    printing rules for trace event as in that code-path 'ops' field wasn't
    initialized.
    
    Signed-off-by: Phil Sutter <phil>

Fix is in the last one, but the previous ones are dependencies.

Comment 4 Phil Sutter 2020-02-24 17:03:10 UTC
Fixed with a small RHEL-only patch:

diff --git a/iptables/xtables-monitor.c b/iptables/xtables-monitor.c
index a5245d1422af9..737c35f2ac60c 100644
--- a/iptables/xtables-monitor.c
+++ b/iptables/xtables-monitor.c
@@ -595,7 +595,9 @@ int xtables_monitor_main(int argc, char *argv[])
        struct mnl_socket *nl;
        char buf[MNL_SOCKET_BUFFER_SIZE];
        uint32_t nfgroup = 0;
-       struct nft_handle h = {};
+       struct nft_handle h = {
+               .family = AF_INET,
+       };
        struct cb_arg cb_arg = {
                .h = &h,
        };
@@ -622,6 +624,9 @@ int xtables_monitor_main(int argc, char *argv[])
                        strerror(errno));
                exit(EXIT_FAILURE);
        }
+       h.ops = nft_family_ops_lookup(h.family);
+       if (!h.ops)
+               xtables_error(PARAMETER_PROBLEM, "Unknown family");
 
        opterr = 0;
        while ((c = getopt_long(argc, argv, "ceht46V", options, NULL)) != -1) {

Comment 10 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


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