Re: [RFC] Suspicious bug in module refcounting

From: Michal Hocko
Date: Tue Feb 10 2009 - 05:31:53 EST


On Tue 10-02-09 13:45:07, Rusty Russell wrote:
> On Tuesday 10 February 2009 01:48:31 Michal Hocko wrote:
> > Based on this change, would it make sense to update sys_accept to change
> > __module_get to try_module_get like in the following patch?
>
> I don't think so:
>
> > /*
> > - * We don't need try_module_get here, as the listening socket (sock)
> > - * has the protocol module (sock->ops->owner) held.
> > + * Socket's owner cannot be in unloading path because there
> > + * must be at least one listening reference
> > */
> > - __module_get(newsock->ops->owner);
> > + if (unlikely(!try_module_get(newsock->ops->owner)))
> > + BUG();
>
> rmmod --wait can make try_module_get fail even if the reference count isn't
> zero.

OK, I though that rmmod --wait waits for refcount==0 and then changes
the state.

> But in this case, we should return an error from the accept call;
> presumably the admin really doesn't want us to keep using the module...
>
> Thanks,
> Rusty.

--
Michal Hocko
L3 team
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/