From owner-freebsd-bugs@FreeBSD.ORG  Sat Feb 28 20:32:40 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BC66A5FC
 for <freebsd-bugs@FreeBSD.org>; Sat, 28 Feb 2015 20:32:40 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A2B1F5FD
 for <freebsd-bugs@FreeBSD.org>; Sat, 28 Feb 2015 20:32:40 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1SKWejR005821
 for <freebsd-bugs@FreeBSD.org>; Sat, 28 Feb 2015 20:32:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 198085] service devfs restart leaks tap devices
Date: Sat, 28 Feb 2015 20:32:40 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: brian@shadowcom.net
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198085-8-HUw1aHMzAn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198085-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-198085-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2015 20:32:40 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198085

--- Comment #1 from brian@shadowcom.net ---
/dev/tap device "instability" may have been due to sysctl setting:

root@tokyo:/etc # ls -l /dev/tap
ls: /dev/tap: No such file or directory
root@tokyo:/etc # sysctl -a | grep net.link.tap.dev
net.link.tap.devfs_cloning: 0
root@tokyo:/etc # sysctl -w net.link.tap.devfs_cloning=1
root@tokyo:/etc # sysctl -a | grep net.link.tap.dev
net.link.tap.devfs_cloning: 1
root@tokyo:/etc # ls -l /dev/tap
crw-------  1 root  wheel  0xa9 Feb 28 15:30 /dev/tap

It is this sysctl that's making the /dev/tap* devices spawn too frequently,
though.  (When set to zero, the "service devfs restart" command doesn't cause
them to continue accumulating.)

Also still unable to see /dev/tap with a glob, but as long as the program
(qemu-devel) can load it by explicit name, it's not the end of the world for
me.

-- 
You are receiving this mail because:
You are the assignee for the bug.