Bug 589614
| Summary: | [rhel5.5] [kernel\network] unable to delete tun device - resource is busy | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Haim <hateya> |
| Component: | tunctl | Assignee: | Jiri Pirko <jpirko> |
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.5 | CC: | abaron, danken, hateya, jpirko, kdube, mgoldboi, rkhan, yeylon, ykaul |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-21 10:21:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Haim
2010-05-06 14:53:27 UTC
The above bug kind of blocks our scenario as we fail to create and manage vms (VDSM). hmm, from "rhevm: port 2(virtio_10_1) entering disabled state" that's obvious that virtio_10_1 is a port in a bridge named "rhevm". Therefore "tunctl -d" fails. If you want to remove the tun device, first release it from the bridge. Hope this clears it. Closing this as notabug, feel free to reopen. 99.9% of the times, `tunctl -d` has no problem operating on a tap device that happens to be connected to a bridge. Yet in this particular case, it failed. The failure persisted even after we deleted virtio_10_1 from the bridge. Our only way to get rid of it was to reboot the machine. Even if our userland behavior is impolite, kernel must respond reasonably. Why is tunctl doing a TUNSETIFF? That seems counterintuitive when you're trying to delete the device. FWIW ip link should be able to delete the device successfully regardless of what state it's in, in fact this is how we discovered many of the races that tun.c had if you deleted a live device :) So to summarise this is a user-space bug. Could someone please reassign this to whatever component that contains tunctl? Thanks! This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Although Herbert suggested this is userspace issue, I disagree. This is kernel issue. It is ok to do TUNSETIFF on existing tun iface and doing this resulting in -EBUSY is bug in this situation. Looks like upstream commit a7385ba21102a90f902055f9f185ca02bf62fa43 is resolving this. This has been backported to rhel5 in commit: commit f986bd670f4307db7ad239bc645d92085e091809 Author: Michael S. Tsirkin <mst> Date: Wed Dec 22 21:11:52 2010 -0500 I believe this should be no longer an issue. Closing this as dup of 672619. Feel free to reopen this when you come across the issue again. *** This bug has been marked as a duplicate of bug 672619 *** |