iptables/ip6tables regressions in deleting rules
Bug #1691752 reported by
Seth Forshee
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Seth Forshee |
Bug Description
2017-05-17 17:11:40 Error restoring autopkgtest:
-----
+ echo 'Remove the firewall rule again'
Remove the firewall rule again
++ id -u test
+ iptables -D OUTPUT -m owner --uid-owner 12345 -j REJECT -p tcp --reject-with tcp-reset
iptables: No chain/target/match by that name.
-----
Can be easily reproduced by hand:
$ sudo iptables -I OUTPUT -m owner --uid-owner $(id -u) -j REJECT -p tcp --reject-with tcp-reset
$ sudo iptables -D OUTPUT -m owner --uid-owner $(id -u) -j REJECT -p tcp --reject-with tcp-reset
iptables: No chain/target/match by that name.
The rule is successfully deleted in xenial/zesty.
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Reverting f77bc5b23fb1 "iptables: use match, target and data copy_to_user helpers" fixes the problem.