Today, I caught it once again and didn't noticed any reconnects (no cERRORs).
It is surely not depends on Jeff's async read patchset, because I used my cifs-3.2-current branch. My branch consists of Steve's master + lockpatchset + smb2 patches. >From another hand, previously I caught it with Jeff's branch (without lockpatchset and smb2 patches). So, that's why the problem is in existing cifs code now. FYI: I checked two files: "buggy" and original, and noticed that the difference between them is located in one place - positions from 2014442 to 2014569 - 126 differences with two equal holes. So, 2014569 - 2014442 + 1 = 128 wrong bytes. Ideas? -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
