Marcelo Tosatti wrote:
So we have a function that takes a lock and conditionally releases it?
Yes, but it is correct: it will only return with the lock held in case
it returns 1, in which case its guaranteed ->write will be called (which
will unlock it).
It should check the range first and/or use some smarter synchronization,
but one thing at a time.
Yes it's correct but we'll get an endless stream of patches to 'fix' it
because it is so unorthodox.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
