Re: [RFC 06/10] kmod: provide sanity check on kmod_concurrent access
From: Luis R. Rodriguez
Date: Wed Dec 14 2016 - 12:13:03 EST
On Wed, Dec 14, 2016 at 05:08:58PM +0100, Petr Mladek wrote:
> On Thu 2016-12-08 11:48:50, Luis R. Rodriguez wrote:
> > Only decrement *iff* we're possitive. Warn if we've hit
> > a situation where the counter is already 0 after we're done
> > with a modprobe call, this would tell us we have an unaccounted
> > counter access -- this in theory should not be possible as
> > only one routine controls the counter, however preemption is
> > one case that could trigger this situation. Avoid that situation
> > by disabling preemptiong while we access the counter.
> I am curious about it. How could enabled preemption cause that
> the counter will get negative?
As the commit log describes today in theory this is not possible
was we have only have one routine controlling the counter. If we
were to expand this then such possibilities become more real.
> Unaccounted access would be possible if put() is called
> without get() or if put() is called before get().
Exactly, so buggy users of the get/put calls in future calls.
I can just drop the preemption disable / enable for now as it
should not be an issue now.
> I do not see a way how the value might get negative when
> the calls are paired and ordered.
Right, this just matches parity with module_put(), its perhaps
*preemptively* too cautious though so I could just drop the
preemption enable/disable for now as that would slow down
things a bit.