Kernel OOPS "Unable to handle kernel NULL pointer dereference"
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I don't think your module is fine if it's causing that problem. If this error occurs after the module is unloaded, you probably want to check your __exit routine to make sure that it's not screwing up any data structures in kernel space. Just out of curiousity, why can't you use the kernel routines copy_to_user and copy_from_user to pass data back and forth? Particularly if you don't have a lot of data to copy, that would probably be a lot safer.
On kmalloc(), if I don't put in GFP_DMA, it gives me random Segmentation faults with a lot of registers & whatnot (I don't know what those are called...) but it doesn't crash. It also works normally when unloaded.