On Fri, 2019-10-18 at 12:43 -0300, Martin Galvan wrote: > El jue., 17 oct. 2019 a las 19:13, Valdis Klētnieks > (<[email protected]>) escribió: > > For starters, the *correct* in-kernel way to deal with this is: > > if (!ptr) { > > printk("You blew it!\n"); > > goto you_blew_it; > > } > > goto statements are harmful. In any case, what I meant was to have > some sort of safety net to prevent exceptions (i.e. if I screw up and > forget a NULL check) from panicking the system.
https://koblents.com/Ches/Links/Month-Mar-2013/20-Using-Goto-in-Linux-Kernel-Code/ > > Also, "current PID" and "my module" aren't two things that can > > correspond.... > > I don't understand what you mean by that. Module code (e.g. an ioctl) > runs as some process. In the case of an ioctl, I'd assume it's the > same PID of the user process. Every time you test whether the PID is the PID of the currently running process, it will be true. Think of the kernel as a privileged shared library, not as a program that userspace happens to communicate with. -- All Rights Reversed.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernelnewbies mailing list [email protected] https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
