linux-kernel - Re: [RFC PATCH 1/1] module: Make wait module's refcount to zero procedure as async

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130913015502.GA20706@shlinux1.ap.freescale.net>
Date:	Fri, 13 Sep 2013 09:55:03 +0800
From:	Peter Chen <peter.chen@...escale.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	<linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/1] module: Make wait module's refcount to zero
 procedure as async

On Fri, Sep 13, 2013 at 10:00:33AM +0930, Rusty Russell wrote:
> Peter Chen <peter.chen@...escale.com> writes:
> > Currently, if module's refcount is not zero during the unload,
> > it waits there until the user decreases that refcount.
> 
> Hi Peter,
> 
>         In practice userspace uses O_NONBLOCK.  In fact, I've been
> thinking of removing the blocking case altogether, since it's not really
> what people want.
> 
> That would solve your problem and make the code simpler.  Thoughts?
> 

So, it will like "Force unload" case, right?
If it is the case, it is better have a warning message to indicate
some users are still using it, since there may null pointer
dereference when the user module has unloaded, and the end user
can understand it may be triggered by wrong module unload sequence.

Thanks.

-- 

Best Regards,
Peter Chen

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