Re: [PATCH v7 13/31] NFSv4.1: Ensure we always run TEST/FREE_STATEID on locks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Anna,

On 10 Nov 2016, at 10:01, Anna Schumaker wrote:
Do you have an estimate for when this patch will be ready? I want to include it in my next bugfix pull request for 4.9.

I haven't posted because I am still trying to get to the bottom of another problem where the client gets stuck in a loop sending the same stateid over
and over on NFS4ERR_OLD_STATEID.  I want to make sure this problem isn't
caused by this fix -- which I don't think it is, but I'd rather make sure. If I don't make any progress on this problem by the end of today, I'll post
what I have.

Read on if interested in this new problem:

It looks like racing opens with the same openowner can be returned out of order by the server, so the client sees stateid seqid of 2 before 1. Then a LOCK sent with seqid 1 is endlessly retried if sent while doing recovery.

It's hard to tell if I was able to capture all the moving parts to describe this problem, though. As it takes a very long time for me to reproduce, and
the packet captures were dropping frames.  I'm working on manually
reproducing it now.

Ben
--
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



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux