| Summary: | ASTERISK-00377: After unloading ztdummy module access to /proc/interrupts will be crashed | ||
| Reporter: | Paul Cadach (pcadach) | Labels: | |
| Date Opened: | 2003-10-13 05:24:15 | Date Closed: | 2004-09-25 02:46:18 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) ztdummy.diff | |
| Description: | Due to re-requesting usb-uhci's IRQ by call to request_irq(..., "usb-uhci", ...), when ztdummy module is unloaded its memory (including string "usb-uhci"!) is freed. Next, when application tries to access /proc/interrupt, kernel will try to generate string with list of modules associated with IRQ. Because memory with "usb-uhci" string (associated with usb-uhci's module interrupt handler) is freed (when ztdummy module has been unloaded), application will crash with SIGSEGV. ****** ADDITIONAL INFORMATION ****** I think this bug is not resolvable without kernel modifications (exporting irq_desc from kernel and walk through IRQ handlers directly from ztdummy or adding function which will return module name associated with IRQ handler). | ||
| Comments: | By: John Todd (jtodd) 2003-10-24 00:38:34 So, is this something that can be resolved through changes to the zaptel package, or is this a problem that is inherent in some Linux kernel handler module? In other words: can this be fixed by anyone reading this ticket? By: Thorsten Lockert (tholo) 2003-10-26 19:21:55.000-0600 I uploaded a patch that fixes this problem. By: Mark Spencer (markster) 2003-10-27 08:44:58.000-0600 Fixed in CVS | ||