richard -rw- weinberger <richard.weinberger@xxxxxxxxx> wrote:
>>>> Thanks for the report. I think I see the problem--after this commit
>>>> nfs4_set_delegation() failures result in nfs4_put_delegation being
>>>> called, but nfs4_put_delegation doesn't free the nfs4_file that has
>>>> already been set by alloc_init_deleg().
>>>>
>>>> Let me think about how to fix that....
>>>
>>> Sorry for the slow response--can you check whether this fixes the
>>> problem?
>>>
>> Yes.
>>
>> With the attached patch the problem can't be reproduced any longer
>> with the prepared test case and current git kernels.
> BTW: Is nobody else fuzz testing NFS? Or are these bugs just more
> likely to hit on UML? This is not the first NFS issue found by Toralf
> using UML and Trinity.
Kernel thread scheduling is likely very different on UML than other
architectures.
My guess is that there could well be be gaps where no kernel thread is
scheduled (because another process is running), followed by resumption of a
thread other than the one which would have been resumed on other
virtualization.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
