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 1719759 - iproute executes commands with the wrong VRF conxext
Summary: iproute executes commands with the wrong VRF conxext
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iproute
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: Andrea Claudi
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-12 13:30 UTC by Matteo Croce
Modified: 2020-11-14 10:52 UTC (History)
3 users (show)

Fixed In Version: iproute-4.18.0-15.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:26:50 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-2019:3602 0 None None None 2019-11-05 22:26:53 UTC

Description Matteo Croce 2019-06-12 13:30:35 UTC
When running in batch mode, iproute can run commands with the wrong VRF associations.

	# ip -b - <<-'EOF'
		link add type vrf table 100
		link set vrf0 up
		link add type dummy
		link set dummy0 vrf vrf0 up
		netns add ns1
	EOF
	# ip -all -b - <<-'EOF'
		vrf exec vrf0 true
		netns exec setsid -f sleep 1h
	EOF
	# ip vrf pids vrf0
	  314  sleep
	# ps 314
	  PID TTY      STAT   TIME COMMAND
	  314 ?        Ss     0:00 sleep 1h

The last batch command should run 'true' with the vrf0 VRF context, and 'sleep 1h' in the default context, in the 'ns1' netns.
But the command later shows that sleep is running with the vrf0 associations.

A series, not yet merged, was posted upstream to fix this:

https://lore.kernel.org/netdev/20190611161031.12898-1-mcroce@redhat.com/T/

Comment 1 Andrea Claudi 2019-06-26 09:59:41 UTC
Fixed upstream. Commits to be backported:

commit 903818fbf9c73dd71793e5829775d2ccc1775af5
Author: Matteo Croce <mcroce>
Date:   Tue Jun 18 16:49:33 2019 +0200

    netns: switch netns in the child when executing commands

commit d81d4ba15d74a51f23f61a2ddb792689e5db95f0
Author: Matteo Croce <mcroce>
Date:   Tue Jun 18 16:49:34 2019 +0200

    ip vrf: use hook to change VRF in the child

commit b2e2922373a6c65ed08b57926e61f3621d89a70a
Author: Matteo Croce <mcroce>
Date:   Tue Jun 18 16:49:35 2019 +0200

    netns: make netns_{save,restore} static

Comment 6 errata-xmlrpc 2019-11-05 22:26:50 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-2019:3602


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