Date: Sun, 06 Oct 2019 02:33:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 123892] [tap] [patch] No buffer space available Message-ID: <bug-123892-227-Hr2RWNLo1e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-123892-227@https.bugs.freebsd.org/bugzilla/> References: <bug-123892-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D123892 Kyle Evans <kevans@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs@FreeBSD.org, | |kevans@freebsd.org Status|Open |Closed Resolution|--- |Overcome By Events Assignee|bugs@FreeBSD.org |kevans@freebsd.org --- Comment #3 from Kyle Evans <kevans@freebsd.org> --- In the 11 years since this issue failed to receive any feedback (=3D( apolo= gies), this looks to be overcome by events. tunread() (in a tuntap(4) world, mind you- so fixed in both tun/tap) holds the tun lock, sets TUN_RWAIT, then uses mtx_sleep(9). tunstart/tunstart_l2 both grab the tun lock and then wakeup(9= ) if if_snd is no longer empty. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-123892-227-Hr2RWNLo1e>