We clearly want to use server inode numbers where possible but this was tricky until some fixes were made last year (which checked for duplicate inode numbers and collisions e.g.) On Tue, May 17, 2011 at 2:54 PM, Pavel Shilovsky <piastryyy@xxxxxxxxx> wrote: > In mount.cifs.8 page we have: "Client generates inode numbers (rather > than using the actual one from the server) by default", but if we look > at the code we can see that > we use server's numbers by default instead: > > http://git.kernel.org/?p=linux/kernel/git/sfrench/cifs-2.6.git;a=blob;f=fs/cifs/connect.c;h=277262a8e82f282d4a32b0ddd4a244bc55e99472;hb=221d1d797202984cb874e3ed9f1388593d34ee22#l859 > > So, where is a error? > > -- > Best regards, > Pavel Shilovsky. > -- > 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 > -- 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
