Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753172Ab0LFO5a (ORCPT ); Mon, 6 Dec 2010 09:57:30 -0500 Received: from mail-gx0-f180.google.com ([209.85.161.180]:60994 "EHLO mail-gx0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750709Ab0LFO53 (ORCPT ); Mon, 6 Dec 2010 09:57:29 -0500 Date: Mon, 6 Dec 2010 09:57:25 -0500 From: Jeff Layton To: Bernhard Walle Cc: sfrench@samba.org, linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cifs: Add information about noserverino Message-ID: <20101206095725.78422138@tlielax.poochiereds.net> In-Reply-To: <1291568855-22604-1-git-send-email-bernhard@bwalle.de> References: <1291568855-22604-1-git-send-email-bernhard@bwalle.de> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3782 Lines: 122 On Sun, 5 Dec 2010 18:07:35 +0100 Bernhard Walle wrote: > In my case I had the problem that 32 bit userspace applications in an > amd64 environment was not able to list the directories of a CIFS-mounted > share. The simple userspace code > > int main(int argc, char *argv[]) > { > DIR *dir; > struct dirent *dirent; > > if (!argv[1]) { > fprintf(stderr, "Usage: %s \n", argv[0]); > return -1; > } > > dir = opendir(argv[1]); > if (!dir) { > perror("Unable to open directory"); > return -1; > } > > while ((dirent = readdir(dir)) != NULL) > puts(dirent->d_name); > > closedir(dir); > > return 0; > } > > was sufficient to trigger the problem. > > I discovered that the problem was that the inodes were too large to fit > in a 32 bit (unsigned long) integer, so the compat_filldir() function > returned -EOVERFLOW. > > While that is okay it would have saved me a some hours of debugging if > the message below would have appeared in my kernel log. > > The target was a Samba server (I guess) of a Buffalo LinkStation Duo > with the unmodified vendor firmware 1.34. > > Signed-off-by: Bernhard Walle > --- > fs/cifs/readdir.c | 23 +++++++++++++++++++---- > 1 files changed, 19 insertions(+), 4 deletions(-) > > diff --git a/fs/cifs/readdir.c b/fs/cifs/readdir.c > index d5e591f..d979826 100644 > --- a/fs/cifs/readdir.c > +++ b/fs/cifs/readdir.c > @@ -773,6 +773,7 @@ int cifs_readdir(struct file *file, void *direntry, filldir_t filldir) > char *tmp_buf = NULL; > char *end_of_smb; > unsigned int max_len; > + int err; > > xid = GetXid(); > > @@ -783,17 +784,31 @@ int cifs_readdir(struct file *file, void *direntry, filldir_t filldir) > > switch ((int) file->f_pos) { > case 0: > - if (filldir(direntry, ".", 1, file->f_pos, > - file->f_path.dentry->d_inode->i_ino, DT_DIR) < 0) { > + err = filldir(direntry, ".", 1, file->f_pos, > + file->f_path.dentry->d_inode->i_ino, DT_DIR); > + if (err < 0) { > cERROR(1, "Filldir for current dir failed"); > + if (err == -EOVERFLOW) { > + cERROR(1, "Server inodes are too large for 32 " > + "bit userspace. You might " > + "consider using 'noserverino' " > + "mount option for this mount."); > + } > rc = -ENOMEM; > break; > } > file->f_pos++; > case 1: > - if (filldir(direntry, "..", 2, file->f_pos, > - file->f_path.dentry->d_parent->d_inode->i_ino, DT_DIR) < 0) { > + err = filldir(direntry, "..", 2, file->f_pos, > + file->f_path.dentry->d_parent->d_inode->i_ino, DT_DIR); > + if (err < 0) { > cERROR(1, "Filldir for parent dir failed"); > + if (err == -EOVERFLOW) { > + cERROR(1, "Server inodes are too large for 32 " > + "bit userspace. You might " > + "consider using 'noserverino' " > + "mount option for this mount."); > + } > rc = -ENOMEM; > break; > } This doesn't look right to me... i_ino is an unsigned long. The code in filldir() is this: unsigned long d_ino; [...] d_ino = ino; if (sizeof(d_ino) < sizeof(ino) && d_ino != ino) { buf->error = -EOVERFLOW; return -EOVERFLOW; } ...so the first condition will return true on a 32-bit arch, but it's not clear to me how you'd get the second one to return true in this situation. -- Jeff Layton -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/