On Tue, 2009-02-17 at 12:29 -0500, Chuck Lever wrote: > I think the correct way to proceed here is to address the original > problem without adding the scope ID check, then explore the scope ID > issue separately. The presenting problem in 11061 affects IPv4 > addresses too if I'm not mistaken, and IPv4 is fairly widely deployed, > so it needs to be fixed now. Absolutely. Where it bit me, and as far as I know all the the respondents, was with IPv4 networks. > If scope ID matching is a problem in nfs_match_client, then it is also > an issue for other places in the NFS client, and should be fixed in > all those places at once, in a single patch that documents the scope > ID matching requirement. Sounds reasonable. I'll change the comment somehow to indicate why the scope_id field is not being compared. Regards, Ian -- Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx> -- 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
