Date: Fri, 23 Sep 2016 11:59:37 +0300 From: "Sergey V. Dyatko" <sergey.dyatko@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: current@freebsd.org Subject: Re: head@r305865: kernel panic after cuse4bsd load. Message-ID: <20160923115937.57427cf6@laptop.minsk.domain> In-Reply-To: <42392f1b-3a9c-7ea5-347d-2c3ea385cbe8@selasky.org> References: <20160923093300.56219da5@laptop.minsk.domain> <9267636a-eeb2-913b-72dd-1bc9d6248eed@selasky.org> <42392f1b-3a9c-7ea5-347d-2c3ea385cbe8@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Sep 2016 09:47:52 +0200 Hans Petter Selasky <hps@selasky.org> wrote: > On 09/23/16 09:34, Hans Petter Selasky wrote: > > On 09/23/16 08:33, Sergey V. Dyatko wrote: > >> Hi, > >> > >> subj. > >> > >> WTR: > >> 1/ kldload cuse > >> 2/ kldload cuse4bsd > >> > >> expected (by me) behavior: 'Cuse4BSD: Please exit all /dev/cuse > >> instances and > >> processes which have used this device.' message and exit, not kernel > >> panic > >> > > > > HI, > > > > You should only load one of them. make_dev() will panic because of > > duplicate /dev/cuse nodes. Do you think it is important that this > > use-case works? > > > > --HPS No. I didn't plan to load cuse module, just pressed Enter too early (kldload cuse[enter]bsd) :) > > This should fix it: > https://svnweb.freebsd.org/changeset/base/306228 > > --HPS > Thanks! -- wbr, tiger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160923115937.57427cf6>