Skip to contentSkip to conversation

Null pointer dereference in pti_exit()

DISCUSSION Stanislaw Gruszka 2 participants 2 messages Mar 26, 2012 – Mar 28, 2012

lore
Share & tools
lore
#0 lore raw

Hi

We have this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=783561

Crash when someone load module and do not have actual pti device. Then misc_deregister(&pti_char_driver) called from pti_exit() will be done without misc_register(&pti_char_driver), which is called from pti_pci_probe().

It is not super critical issue since if somebody who do not have pti device have no reason to load modules, but I guess would be good to fix this.

Thanks
Stanislaw

#1 lore raw
Quoted 5 lines · Stanislaw Gruszka

Hi

We have this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=783561

Quoted 9 lines

Crash when someone load module and do not have actual pti device. Then misc_deregister(&pti_char_driver) called from pti_exit() will be done without misc_register(&pti_char_driver), which is called from pti_pci_probe().

It is not super critical issue since if somebody who do not have pti device have no reason to load modules, but I guess would be good to fix this.

Thanks for the email. I just got back from a 3 month sabbatical so I am slowly getting back into the real world and how to be a computer engineer.

Yes, I am not sure why someone would want to configure their kernel to load a PTI module when there is not one on the platform to begin with. So that is a configuration problem of a user. But I'll look at it and see if I think of anything; be a good exercise to re-jog my memory.

Thanks,
Jay

Quoted 2 lines

Thanks
Stanislaw

Signature · 3 lines
J (James/Jay) Freyensee
Storage Technology Group
Intel Corporation