No, that's not reasonable. Sometimes, when you know that some situations are "impossible", you very much want to kernel panic. This isn't just some command-line argument handling that you can bail out with an error message. The input is not coming directly from the user--it's coming from other kernel interfaces. There shouldn't be any "unexpected inputs" in some cases, like this one.
On Dec 18, 3:43 am, Erik Larsson <[email protected]> wrote: > I can't imagine that the intended behavior of the kernel extension when > passed unexpected input would be to cause a kernel panic? > A log entry and an error code returned seems more reasonable. > > - Erik > > mike glass wrote: > > Thanks for the response. It prompted me to do more digging and I > > found that whenever there's a kernel panic, VMWare is starting, so > > I'll drag this to their support forums. > > > On Dec 18, 1:29 am, Amit Singh <[email protected]> wrote: > > >> MacFUSE is seeing a flag passed to it in open() that it doesn't > >> expect. Do you have steps to reproduce this? > > >> Amit > > >> On Dec 17, 2:11 pm, mike glass <[email protected]> wrote: > > >>> Hey there. I've received a number of kernel panics referencing > >>> macfuse and was wondering if I could get some help hunting down the > >>> culprit. > > >>> here are two of the panic logs: > > >>> Wed Dec 17 17:02:00 2008 > >>> panic(cpu 1 caller 0x867E95F6): "MacFUSE: What kind of a flag is this > >>> (0)?"@/work/macfuse/core/10.5/fusefs/fuse_file.h:69 > >>> Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) > >>> 0x56bdf898 : 0x12b4f3 (0x45b13c 0x56bdf8cc 0x1335e4 0x0) > >>> 0x56bdf8e8 : 0x867e95f6 (0x867ef1f8 0x0 0x56bdf918 0x867d901b) > >>> 0x56bdf988 : 0x1f65e6 (0x56bdf9b0 0x0 0x0 0x922f000) > >>> 0x56bdf9d8 : 0x1eb6de (0xc1f1ab0 0x0 0x922f000 0x922f000) > >>> 0x56bdfa38 : 0x1ecc33 (0x56bdfb6c 0x56bdfb54 0x56bdfa5c 0x0) > >>> 0x56bdfb48 : 0x1d8732 (0x56bdfb6c 0x0 0x0 0x1af514) > >>> 0x56bdfcd8 : 0x56b944d4 (0xc707b40 0x0 0x0 0x0) > >>> 0x56bdfe28 : 0x56d8f21a (0xdeb5300 0xde8fb80 0x56bdfe58 0x9b8e880) > >>> 0x56bdfe48 : 0x412976 (0xdeb5300 0xde8fb80 0x1 0x3ecd96) > >>> 0x56bdfea8 : 0x414219 (0xde8fb80 0xdeb5300 0x56bdff0c 0x14cb9c00) > >>> 0x56bdff28 : 0x413a7d (0xde8fb80 0xbe1e300 0x0 0x3f1bef) > >>> 0x56bdff78 : 0x415111 (0xde8fb80 0x8 0x56bdffac 0x1) > >>> 0x56bdffc8 : 0x1a017c (0xb5a5e50 0x0 0x1a30b5 0x79693c8) > >>> Backtrace terminated-invalid frame pointer 0 > >>> Kernel loadable modules in backtrace (with dependencies): > >>> com.apple.driver.DiskImages.FileBackingStore(195.2.2) > >>> @0x56b93000->0x56b95fff > >>> dependency: com.apple.driver.DiskImages.KernelBacked > >>> (195.2.2)@0x56d8d000 > >>> dependency: com.apple.driver.DiskImages(195.2.2)@0x7ee000 > >>> dependency: com.apple.iokit.IOStorageFamily(1.5.5) > >>> @0x667000 > >>> > >>> com.apple.driver.DiskImages.KernelBacked(195.2.2)@0x56d8d000->0x56d99fff > > >>> dependency: com.apple.driver.DiskImages(195.2.2)@0x7ee000 > >>> dependency: com.apple.iokit.IOStorageFamily(1.5.5) > >>> @0x667000 > >>> com.google.filesystems.fusefs(2.0.1)@0x867dd000->0x867f0fff > > >>> BSD process name corresponding to current thread: kernel_task > > >>> Mac OS version: > >>> 9G55 > > >>> Kernel version: > >>> Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; > >>> root:xnu-1228.9.59~1/RELEASE_I386 > >>> System model name: MacBookPro5,1 (Mac-F42D86C8) > > >>> Tue Dec 16 17:57:25 2008 > >>> panic(cpu 1 caller 0x880905F6): "MacFUSE: What kind of a flag is this > >>> (0)?"@/work/macfuse/core/10.5/fusefs/fuse_file.h:69 > >>> Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) > >>> 0x56f8f898 : 0x12b4f3 (0x45b13c 0x56f8f8cc 0x1335e4 0x0) > >>> 0x56f8f8e8 : 0x880905f6 (0x880961f8 0x0 0x56f8f918 0x56e3a01b) > >>> 0x56f8f988 : 0x1f65e6 (0x56f8f9b0 0x0 0x0 0x874e9c0) > >>> 0x56f8f9d8 : 0x1eb6de (0xa4c9f30 0x0 0x874e9c0 0x874e9c0) > >>> 0x56f8fa38 : 0x1ecc33 (0x56f8fb6c 0x56f8fb54 0x56f8fa5c 0x9a26d40) > >>> 0x56f8fb48 : 0x1d8732 (0x56f8fb6c 0x0 0x0 0x87fec000) > >>> 0x56f8fcd8 : 0x50d844d4 (0x79ae380 0x0 0x0 0x0) > >>> 0x56f8fe28 : 0x5760921a (0xe65c780 0xe451900 0x56f8fe58 0x12c56a00) > >>> 0x56f8fe48 : 0x412976 (0xe65c780 0xe451900 0x1 0x3ecd96) > >>> 0x56f8fea8 : 0x414219 (0xe451900 0xe65c780 0x56f8ff0c 0x1294d0e0) > >>> 0x56f8ff28 : 0x413a7d (0xe451900 0xd02f240 0x0 0x3f1bef) > >>> 0x56f8ff78 : 0x415111 (0xe451900 0x8 0x56f8ffac 0x1) > >>> 0x56f8ffc8 : 0x1a017c (0xaf78670 0x0 0x1a30b5 0xef0de40) > >>> Backtrace terminated-invalid frame pointer 0 > >>> Kernel loadable modules in backtrace (with dependencies): > >>> com.apple.driver.DiskImages.FileBackingStore(195.2.2) > >>> @0x50d83000->0x50d85fff > >>> dependency: com.apple.driver.DiskImages.KernelBacked > >>> (195.2.2)@0x57607000 > >>> dependency: com.apple.driver.DiskImages(195.2.2)@0x7e9000 > >>> dependency: com.apple.iokit.IOStorageFamily(1.5.5) > >>> @0x662000 > >>> > >>> com.apple.driver.DiskImages.KernelBacked(195.2.2)@0x57607000->0x57613fff > > >>> dependency: com.apple.driver.DiskImages(195.2.2)@0x7e9000 > >>> dependency: com.apple.iokit.IOStorageFamily(1.5.5) > >>> @0x662000 > >>> com.google.filesystems.fusefs(2.0.1)@0x88084000->0x88097fff > > >>> BSD process name corresponding to current thread: kernel_task > > >>> Mac OS version: > >>> 9G55 > > >>> Kernel version: > >>> Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; > >>> root:xnu-1228.9.59~1/RELEASE_I386 > >>> System model name: MacBookPro5,1 (Mac-F42D86C8) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
