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 1540917 - nft map with ipv6 address type key and integer type value can not be added
Summary: nft map with ipv6 address type key and integer type value can not be added
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nftables
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 7.6
Assignee: Phil Sutter
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 1554861
TreeView+ depends on / blocked
 
Reported: 2018-02-01 10:25 UTC by Li Shuang
Modified: 2018-10-30 10:38 UTC (History)
6 users (show)

Fixed In Version: nftables-0.8-8.el7
Doc Type: No Doc Update
Doc Text:
A release note should describe in detail a new feature being introduced into the product. A release note is NOT a bug, errata enhancement, rebase, known issue, Technology Preview or deprecated functionality description; for these, select the corresponding Doc Type option.
Clone Of:
Environment:
Last Closed: 2018-10-30 10:38:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3154 0 None None None 2018-10-30 10:38:36 UTC

Comment 4 Phil Sutter 2018-05-22 08:53:15 UTC
Should be fixed by the following upstream commit:

commit 483e5ea7167e1537accf4cb083b88a8beea8f834
Author: Florian Westphal <fw>
Date:   Tue Mar 27 09:29:54 2018 +0200

    src: avoid errouneous assert with map+concat
    
    Phil reported following assert:
    
    add rule ip6 f o mark set ip6 saddr . ip6 daddr . tcp dport \
                            map { dead::beef . f00::. 22 : 1 }
    nft: netlink_linearize.c:655: netlink_gen_expr: Assertion `dreg < ctx->reg_low' failed.
    
    This happens because "mark set" will allocate one register (the dreg),
    but netlink_gen_concat_expr will populate a lot more register space if
    the concat expression strings a lot of expressions together.
    
    As the assert is useful pseudo-reserve the register space as per
    concat->len and undo after generating the expressions.
    
    Reported-by: Phil Sutter <phil>
    Signed-off-by: Florian Westphal <fw>

Comment 11 errata-xmlrpc 2018-10-30 10:38:13 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/RHBA-2018:3154


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