The reason of panic while 'cat /proc/ioports' [Re: SS_CAP_STATIC_MAP and...]

 Thanks to all for explanations and interesting discussion. Yes, I'm 
working with 2.4,
and I hope we will have more  consistent approach  in 2.5 :-).

 The reason for kernel panic at 'cat /proc/ioports' looks simple. Each 
resource has a name:

 struct resource {
        const char *name;
        ...
};

This name is not copied in __request_region(), and 'name' points to some 
string
constant in a module space. This pointer becomes invalid after module 
unloading, so
dereferencing it in do_resource_list() causes 'Unable to handle....' bug.

Dmitry




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en