Re: [PATCH] xencommons: Attempt to load blktap driver

[George Dunlap <george.dunlap@eu.citrix.com>]

On 16/05/12 10:57, Ian Campbell wrote:
>>> The blktap detection code is necessarily OS-specific. I previously
>>> discounted it because of the possibility of a race between the
>>> completion of modprobe and the driver actually registering enough for
>>> detection to succeed. Maybe I was too pessimistic or someone has a
>>> bright idea?
>> modprobe only exits when the driver's init function completed,
>> at which point the driver can be expected to be in a usable state.
> OK, so maybe that works then.
So what's the plan?  Options seem to be:
1. Put this on the blocker list, so it definitely gets done before release
2. Accept the patch that started this thread (or a version of it), and 
put "do it right" on the "nice-to-have" list.  I can do it if I get a 
chance.
3. Someone can volunteer who can prioritize it.

  -George