Could you please unscribe me from this list -----Original Message----- From: samba-technical-bounces@xxxxxxxxxxxxxxx [mailto:samba-technical-bounces@xxxxxxxxxxxxxxx] On Behalf Of Pavel Shilovsky Sent: Friday, April 27, 2012 6:29 PM To: Dan Carpenter Cc: Steve French; linux-cifs@xxxxxxxxxxxxxxx; kernel-janitors@xxxxxxxxxxxxxxx; samba-technical@xxxxxxxxxxxxxxx; Josef Bacik Subject: Re: [patch] cifs: fix revalidation test in cifs_llseek() 20 апреля 2012 г. 1:06 пользователь Dan Carpenter <dan.carpenter@xxxxxxxxxx> написал: > This test is always true so it means we revalidate the length every > time, which generates more network traffic. This was introduced in > 06222e491e "fs: handle SEEK_HOLE/SEEK_DATA properly in all fs's that > define their own llseek". > > Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx> > --- > Josef, there were three other places that had this same problem but I > think they've all been fixed now. Except that I had a question about > nfs_file_llseek(). Isn't that reversed? It seems like it only > revalidates when it's not supposed to. I chose to copy what > fuse_file_llseek() does instead. > > diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c > index d342128..97d26c7 100644 > --- a/fs/cifs/cifsfs.c > +++ b/fs/cifs/cifsfs.c > @@ -695,7 +695,7 @@ static loff_t cifs_llseek(struct file *file, loff_t offset, int origin) > * origin == SEEK_END || SEEK_DATA || SEEK_HOLE => we must revalidate > * the cached file length > */ > - if (origin != SEEK_SET || origin != SEEK_CUR) { > + if (origin == SEEK_SET || origin == SEEK_CUR) { > int rc; > struct inode *inode = file->f_path.dentry->d_inode; > In this case the semantic contradict the comment above. May be it should be "if (origin != SEEK_SET && origin != SEEK_CUR)"? -- Best regards, Pavel Shilovsky. ::DISCLAIMER:: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, Modification, distribution and/or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
