Has this been fixed yet?

I posted before but nobody seems to have read it.
I get his _every_time_ I unload emu10k1 (OSS) module on 2.6.0-test1:

Call Trace:
[<c018e261>] devfs_remove+0x9e/0xa0
[<c013898a>] unmap_vmas+0xcb/0x214
[<d29e3e2d>] oss_cleanup+0x2b/0xed [sound]
[<c0129c1e>] sys_delete_module+0x152/0x1a8
[<c0130064>] generic_file_aio_write_nolock+0x8a7/0xa6a
[<c013be3c>] sys_munmap+0x57/0x75
[<c0108f81>] sysenter_past_esp+0x52/0x71 

And I'm not using devfs.

Nope:

	http://bugme.osdl.org/show_bug.cgi?id=963

Feel free to add your comments to this bug to let people know about it.

thanks,

greg k-h

btw, which part of the kernel is responsible for finding out if devfs is in use or not _even_ when devfs is not compiled in? There seems to be a problem here, why is there any code running in my kernel to find out if devfs "exists" or not even when its not compiled in? Its not available as module is it? According to that osdl bug report page it seems this thing is almost unnoticed.
I really don't like to see error messages even if they are harmless...(a tiny bit of my cpu power was used to remove a virtual device that doesn't exist, and also to display the error message on the screen, and not to mention that it actually increases the kernel image size by a few bytes using a few extra bytes of my precious ram)