Re: [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.

> Couldn't the cxacru instance pointer to the proc_read function be set to NULL before unloading?

The problem is reads that started (on some other CPU) before you started shutting things down
(eg: but setting this to null or whatever other method you like) and only finish after you have
finished shutting things down.  Or rather, never finish at all because the code they are executing
has been deleted from the kernel, causing an Oops.  This is not our problem: we can't do anything
about it: remove_proc_entry needs to be fixed so that it waits for all readers/writers of the proc
file to finish before returning, IMO.

Best wishes,

Duncan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.
  - From: Simon Arlott <[email protected]>
- Re: [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.
  - From: Duncan Sands <[email protected]>
- Re: [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.
  - From: Simon Arlott <[email protected]>

Prev by Date: Re: Free Linux Driver Development!
Next by Date: Re: Unidentified Intel wifi network card
Previous by thread: Re: [PATCH 1/3] usbatm: Allow sub-drivers to handle calls to atm_proc_read.
Next by thread: [PATCH 2/3] cxacru: Poll for device status more frequently.
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]