search for: smb_refill_dircach

...lt -5, setting invalid smb_retry: new pid=7299, generation=4 (this continued up to "generation=7") smb_get_length: recv error = 5 smb_request: result -5, setting invalid smb_retry: caught signal smb_retry: caught signal smb_proc_readdir_long: name=nspect.exe, entries=624, rcls=2, err=1 smb_refill_dircache: readdir failed, result=-23 smb_proc_readdir_long: name=\RECYCLED\*, entries=0, rcls=2, err=1 smb_refill_dircache: readdir failed, result=-23 smb_proc_readdir_long: name=\Program Files\*, entries=0, rcls=2, err=1 smb_refill_dircache: readdir failed, result=-23 smb_proc_readdir_long: name=\My Docum...

Has anyone else seen these? smb_proc_readdir_long: name=, entries=117, rcls=1, err=123 smb_refill_dircache: readdir failed, result=-2 I get them when trying to read a particular directory from a NT4 SP4 (?) server. % /bin/ls -alF foo total 0 % The directory in question has 718 files, all with rather long names. This is on a Linux 2.2.12 patched with my smbfs-nls-filename patch. I'd like to know...

This is a problem I get with various versions of Samba, up to and including 2.0.7. (The version shipped with Debian.) I have an NT machine (4.0, service-pack 3 using NTFS) exporting a filesystem to Linux through smbmount. Specific directories are not browsable. By that I mean that "ls *" comes up blank, however if you know the filename, "ls foo.txt" will still find the

Hi- I'm working on a graphical interface to smbclient/smbmount/smbumount. As part of its operation, it will mount shares in directories under a user's home directory. I've run into a bit of a problem regarding the distributions of the mount utilities, specifically on Redhat 5.1/5.2. They are shipping an RPM with smbfs 2.0.1, which is known to have a security hole... so it should

...rence to the + * name instead of having to copy it. + */ +struct cache_dirent { + ino_t ino; + unsigned long pos; + int len; + char * name; +}; + +struct cache_head * smb_get_dircache(struct dentry *); +void smb_init_dircache(struct cache_head *); +void smb_free_dircache(struct cache_head *); +int smb_refill_dircache(struct cache_head *, struct dentry *); +void smb_add_to_cache(struct cache_head *, struct cache_dirent *, off_t); +int smb_find_in_cache(struct cache_head *, off_t, struct cache_dirent *); +void smb_invalid_dir_cache(struct inode *); + +#endif /* __KERNEL__ */ + +#endif /* _LINUX_SMB_FS_H */ diff...

...00 00000002 c0de9000 May 17 00:03:43 core kernel: c0cf9c00 c0306ee4 c0349b78 c01b7bfa c0009380 c13ddec0 00000000 00000000 May 17 00:03:43 core kernel: Call Trace: [smb_init_dircache+11/28] [smb_proc_readdir_long+183/968] [start_next_request+78/96] [ide_intr+228/240] [smb_proc_readdir+35/60] [smb_refill_dircache+31/100] [smb_readdir+81/384] May 17 00:03:43 core kernel: [smb_dir_open+67/80] [sys_getdents+245/352] [filldir+0/132] [smb_readdir+0/384] [system_call+52/64] May 17 00:03:43 core kernel: Code: 8b 43 18 a8 01 75 0d 68 a9 0f 26 c0 e8 12 49 ff ff 83 c4 04 6. Run updatedb across the network...