Re: [PATCH] tun driver use private linked list.

[Max Krasnyansky <maxk@xxxxxxxxxxxx>]

At 12:59 PM 10/9/2003, Stephen Hemminger wrote:
>On Thu, 09 Oct 2003 11:45:31 -0700
>Max Krasnyansky <maxk@xxxxxxxxxxxx> wrote:
>
>> Actually in case of persistent devices we can not let the module go away. 
>> Because it has
>> important info like user id of the owner and stuff which is not stored 
>> anywhere else. 
>> It also provides device name reservation, UML folks use it for example to 
>> reserve certain 
>> devices to a certain users. If module goes away admin will have to recreate 
>> those devices 
>> again. TUN/TAP devices are created in ioctl and since vfs layer already 
>> holds a reference, 
>> like you said, it's safe for us to just do __module_get()/module_put(). 
>
>I think letting the admin do what he requests is the right thing.  The 
>philosophy of
>module unload has changed: with 2.4 it was "don't let admin unload the network
>element if anything is using it"; now it is "let the admin unload any module
>and cleanup as necessary".  
Yeah, I don't necessarily agree with that :). But I guess you can argue that 
only admin can unload the module. And he probably knows what he's doing.

Max