It's a null-pointer dereference in fuse_vnop_blockmap(). The F_LOG2PHYS code path causes that function to be called with a certain parameter as NULL. I was not checking it for NULL-ness. Thanks for finding the bug.
I've fixed it in the source tree. Amit On Oct 16, 8:49 pm, Erik Larsson <[email protected]> wrote: > Hi, > > Has anyone noticed that you can easily provoke a kernel panic just by > invoking the F_LOG2PHYS fcntl on any file residing on a MacFUSE mount? > Steps to reproduce: > - Mount a volume with your favorite MacFUSE driver (loopback.c is always > a good one). > - Compile and run the included demo utility, log2phys.c, for any file on > the MacFUSE mount. > - Voila, kernel panic. (Confirmed on Leopard and Snow Leopard with > MacFUSE 2.0.3.) > > Regards, > > - Erik > > log2phys.c > 1KViewDownload --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
