2012/2/28 Steve French <[email protected]>: > I don't think we can do this for the cifs case - 49 blocking locks and > we would deadlock our system (a pending write could block forever) - > for smb2.2 it makes more sense. I don't think it actually causes a > problem to exceed 50 blocks locks - but if we want to count blocking > locks we will have to limit the maximum number of blocking locks to 2 > or 3 less than maxmpx and not allow blocking locks if maxmpx is lower > than 3. >
Seems reasonable. We can easy add such a check to now exceed maxmpx - 3 value. -- 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
