Date: Sat, 18 Nov 2017 11:30:00 +0100 From: "Kristof Provost" <kristof@sigsegv.be> To: "Jukka A. Ukkonen" <jau789@gmail.com> Cc: questions@freebsd.org Subject: Re: 10.4-stable systematically crashing inside pselect() when a tun device is used Message-ID: <98FCCAA8-B52E-462E-A5FF-4A58FE586253@sigsegv.be> In-Reply-To: <de8b485e-b3d4-82dd-0064-403679904086@gmail.com> References: <de8b485e-b3d4-82dd-0064-403679904086@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Nov 2017, at 10:27, Jukka A. Ukkonen wrote: > Hello all, > > As briefly stated in the subject I have a 10-stable system on > which I have been testing a program which opens either a tun > device or a tap device, waits in pselect() for the descriptor > to become readable, and then proceeds to read the packet/frame. > When using a tun descriptor the pselect() call always panics the > kernel with the complaints shown in the photo below. When using > a tap device the same code works just fine. The mailing lists don’t allow attachments. You’ll have to get a text version of the backtrace. (Set dumpdev="AUTO" in /etc/rc.conf, reboot, trigger the crash. Look for /var/crash/core.txt.0) Regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98FCCAA8-B52E-462E-A5FF-4A58FE586253>