Pavel Emelyanov wrote:
> Balbir Singh wrote:
>> Pavel Emelyanov wrote:
>>> Please, try with this patch too:
>>>
>>> diff --git a/fs/locks.c b/fs/locks.c
>>> index c0fe71a..f599508 100644
>>> --- a/fs/locks.c
>>> +++ b/fs/locks.c
>>> @@ -1423,7 +1423,7 @@ int generic_setlease(struct file *filp, 
>>>     locks_copy_lock(new_fl, lease);
>>>     locks_insert_lock(before, new_fl);
>>>
>>> -   *flp = fl;
>>> +   *flp = new_fl;
>>>     return 0;
>>>
>>>  out:
>>>
>> Hi, Pavel,
>>
>> You did not signoff on the patch.
> 
> I did not, but this is just a patch to test. I know, that it
> most likely fixes the problem, but since Kamalesh didn't tell
> us how he had triggered it, I'd like him to Ack it :)
> 
> Thanks,
> Pavel
> 
> 

Ok, just wanted to let you know in case you missed it out.
In case Andrew picked it up. That's all!


-- 
        Warm Regards,
        Balbir Singh
        Linux Technology Center
        IBM, ISTL
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to