Re: vn.ko load/unload/mount = panic

In message <[EMAIL PROTECTED]>, Peter Edwards writes: >After reading the rest of the discussion on this thread, and moving out >of my depth a little, I assume vn should probably be using >disk_create()/disk_destroy(), and attaching its softc to the disk object >rather than the device object. (How

Re: vn.ko load/unload/mount = panic

Nick Hibma wrote: > > Correct me if I am wrong, but I don't think you actually have to > disassociate any dev_t's from the driver (by clearing the si_drv[12] > fields) because we call destroy_dev and cdevsw_remove, so any later uses > of dev_t's get an error because the device has gone away. > >

Re: vn.ko load/unload/mount = panic

> In message , Nick Hibma wri > tes: > > > >Correct me if I am wrong, but I don't think you actually have to > >disassociate any dev_t's from the driver (by clearing the si_drv[12] > >fields) because we call destroy_dev and cdevsw_remove, so any

Re: vn.ko load/unload/mount = panic

In message <[EMAIL PROTECTED]>, Mike Smith writes: >> In message , Nick Hibma wri >> tes: >> > >> >Correct me if I am wrong, but I don't think you actually have to >> >disassociate any dev_t's from the driver (by clearing the si_drv[12] >> >field

Re: vn.ko load/unload/mount = panic

In message , Nick Hibma wri tes: > >Correct me if I am wrong, but I don't think you actually have to >disassociate any dev_t's from the driver (by clearing the si_drv[12] >fields) because we call destroy_dev and cdevsw_remove, so any later uses >

Re: vn.ko load/unload/mount = panic

Correct me if I am wrong, but I don't think you actually have to disassociate any dev_t's from the driver (by clearing the si_drv[12] fields) because we call destroy_dev and cdevsw_remove, so any later uses of dev_t's get an error because the device has gone away. Apart from that I don't think w

Re: vn.ko load/unload/mount = panic

I had a longer look at this, and a more complete patch is logged as PR kern/18270 (try at your own risk: it works for me). I'd appreciate someone more experienced having a look at it and commenting. Cheers, Peter. Wilko Bulte wrote: > > On Wed, Apr 26, 2000 at 04:25:46PM +0100, Peter Edwards (l

Re: vn.ko load/unload/mount = panic

On Wed, Apr 26, 2000 at 04:25:46PM +0100, Peter Edwards (local) wrote: How about send-pr ing this stuff? Wilko > Hi, > After a (very) quick look at the source it looks like there's a missing > cdevsw_remove() missing from the MOD_UNLOAD/MOD_SHUTDOWN event handling > I haven't t

Re: vn.ko load/unload/mount = panic

Sorry, I think that fix is incomplete (though it'll prolly stop the crashes). I think there should be a destroy_dev() call for each created device in the MOD_UNLOAD case also. I'll make a patch and send-pr it once I get back to my home machine, unless someone more experienced feels the need to do

Re: vn.ko load/unload/mount = panic

Hi, After a (very) quick look at the source it looks like there's a missing cdevsw_remove() missing from the MOD_UNLOAD/MOD_SHUTDOWN event handling I haven't time to test it, but try this: *** vn.c.oldWed Apr 26 16:23:03 2000 --- vn.cWed Apr 26 16:24:06 2000 *** *** 762,76

vn.ko load/unload/mount = panic

Hi, I've already submitted this crash report earlier but it seems that developers in -current list are too busy discussing whether Matt allowed to commit his SMP work into 4.0 to pay attention to "ordinary" panic reports :-(. Following is slightly simplified course of actions which is known to pr