On Tue, Jan 15, 2013 at 1:01 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > We've had a long-standing problem with DFS referral points. CIFS servers > generally try to make them look like directories in FIND_FIRST/NEXT > responses. When you go to try to do a FIND_FIRST on them though, the > server will then (correctly) return STATUS_PATH_NOT_COVERED. Mostly this > manifests as spurious EREMOTE errors back to userland. Why would we ever return STATUS_PATH_NOT_COVERED (converted to EREMOTE)? If we do a find first on a directory and get status path not covered - why don't we simply chase the DFS referral then rather than greatly slow down findfirst? -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
