4cb8c3593b
The sk_prot is irda's own set of protocol handlers, so irda should statically know what that function is anyway, without using an indirect pointer. And as it happens, we know *exactly* what that pointer is statically: it's NULL, because irda doesn't define a disconnect operation. So calling that function is doubly wrong, and will just cause an oops. Reported-by: Martin Lang <mlg.hessigheim@gmail.com> Cc: Samuel Ortiz <samuel@sortiz.org> Cc: David Miller <davem@davemloft.net> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| ircomm | ||
| irlan | ||
| irnet | ||
| af_irda.c | ||
| discovery.c | ||
| irda_device.c | ||
| iriap_event.c | ||
| iriap.c | ||
| irias_object.c | ||
| irlap_event.c | ||
| irlap_frame.c | ||
| irlap.c | ||
| irlmp_event.c | ||
| irlmp_frame.c | ||
| irlmp.c | ||
| irmod.c | ||
| irnetlink.c | ||
| irproc.c | ||
| irqueue.c | ||
| irsysctl.c | ||
| irttp.c | ||
| Kconfig | ||
| Makefile | ||
| parameters.c | ||
| qos.c | ||
| timer.c | ||
| wrapper.c | ||