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 1465599 - Fix multiple issues with xt action
Summary: Fix multiple issues with xt action
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iproute
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Phil Sutter
QA Contact: Jaroslav Aster
URL:
Whiteboard:
: 1513973 (view as bug list)
Depends On:
Blocks: 1470965
TreeView+ depends on / blocked
 
Reported: 2017-06-27 17:42 UTC by Jaroslav Aster
Modified: 2018-04-10 14:30 UTC (History)
5 users (show)

Fixed In Version: iproute-4.11.0-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1326726
Environment:
Last Closed: 2018-04-10 14:28:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0815 0 None None None 2018-04-10 14:30:42 UTC

Description Jaroslav Aster 2017-06-27 17:42:47 UTC 
Bug for remaining issues from bug bz#1326726. Still not fully fixed. Tested on

iproute-3.10.0-87.el7

+++ This bug was initially created as a clone of Bug #1326726 +++

--- Additional comment from Phil Sutter on 2017-05-18 14:19:34 EDT ---

Hi Jaroslav,

(In reply to Jaroslav Aster from comment #6)
> Hi Phil,
> 
> unfortunately I see still a lot of fails and segfaults in my test case. Yes,
> there is some progress, but it is not definitely fixed. See
> 
> http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2017/04/18159/
> 1815921/3752192/54687568/TESTOUT.log

Yes, xt action is still buggy. The segfaults are all related to using any of the NAT targets (SNAT, DNAT, MASQUERADE and REDIRECT). I found the reason why it segfaults (which happens in libipt, BTW) and I have a workaround at hand. Problem is, these targets will still refuse to work then, just the segfault does not happen anymore.

Other non-functional targets are internal ones (ACCEPT, DROP, RETURN). This is also a known issue upstream.

You see, xt action has very limited use even upstream and so I don't see much sense in trying to get all these things functional.
Comment 1 Phil Sutter 2017-07-26 09:23:54 UTC 
Upstream commit to backport (which prevents the segfault at least):

commit f6fc1055e41a8a924313c336b39b9ffe0c86938b
Author: Phil Sutter <psutter>
Date:   Tue May 23 15:40:57 2017 +0200

    tc: m_xt: Prevent a segfault in libipt
    
    This happens with NAT targets, such as SNAT, DNAT and MASQUERADE. These
    are still not usable with this patch, but at least tc doesn't crash
    anymore when one tries to use them.
    
    Signed-off-by: Phil Sutter <phil>
Comment 3 Jaroslav Aster 2017-11-08 13:32:36 UTC 
Hi Phil,

I can confirm that there are no segfaults anymore, but there are still a lot of issues to solve.

I'm not sure what we should do with this bug.
Comment 4 Phil Sutter 2017-11-08 15:15:45 UTC 
Hi Jaroslav,

(In reply to Jaroslav Aster from comment #3)
> Hi Phil,
> 
> I can confirm that there are no segfaults anymore, but there are still a lot
> of issues to solve.
> 
> I'm not sure what we should do with this bug.

There are conceptual problems with xt action, I don't think it is even possible to address all of them. Assuming that anyone using it should be aware of its limitations, I'd say making sure tc doesn't crash is about the best we can do.
Comment 6 Phil Sutter 2017-12-13 17:19:19 UTC 
*** Bug 1513973 has been marked as a duplicate of this bug. ***
Comment 9 errata-xmlrpc 2018-04-10 14:28:47 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-2018:0815
Note You need to log in before you can comment on or make changes to this bug.