Sorry about the previous message...
Note that the maintainer listed in MAINTAINERS is no longer active, so
perhaps it should be updated?
I've found a problem with SMBFS and *really* long pathnames. It causes
the kernel to OOPS, and sometimes corrupts the kernel stack. I've even had
it corrupt the SLAB allocator so bad that no binary could be run :)
REPORTING-BUGS format answers, let me know if there is anything else you
would like to know:
1. SMBFS OOPS on really long pathnames
2. Here's my test setup:
2.2.9 stock SMP kernel on a UP system. SMBFS is in the kernel. Using
samba 2.0.2's smbmount.
2.0.36 stock SMP kernel on an SMP system. Samba 1.9.18p8 server.
Exporting a root share. The share contains a recursive directory
structure:
/etc: inet -> .
There is also an *empty* fs directory in /etc
To reproduce the OOPS, simply cd to /etc/inet/inet/inet.. (as far as you
can go until directory not found is returned), then into fs.
samba's chopping of directory names is incorrect in the version of the
server that is running, and will show an fs directory inside the fs
directory. Continue to traverse the fs directories until the kernel
on the client OOPS's.
One can argue that the version of samba on the server is the problem --
it should be better behaved, however, I think this error would occur on
a legitimate directory, if the path structure was long enough (NT can
have a 65535 character path)
While running this the server samba reports the following style of error
message:
ERROR: string overflow by 33677 in safe_strcpy
[\etc\inet\inet\inet\inet\inet\inet\inet\inet\inet\]
ERROR: string overflow by 1 in safe_strcat
[/etc/inet/inet/inet/inet/inet/inet/inet/inet/inet/]
This is repeated several times, with the value of the first string
overflow increasing on each iteration into a new fs directory.
The client SMBFS reports the following error message:
May 17 00:03:42 core kernel: smb_setup_header: Aieee, xmit len > packet!
len=34780, size=4096
Again, this is repeated with the value getting larger the farther we traverse
down the dir structure.
3. SMBFS, kernel, samba, OOPS
4. client: Linux version 2.2.9 (root@straylight) (gcc version 2.7.2.3) #1 SMP
Fri May 14 06:46:55 PDT 1999
server: Linux version 2.0.36 (root@straylight) (gcc version 2.7.2.3) #1 Sun
Dec 20 20:35:25 PST 1998
client is uni-processor 486-33, server is dual-processor P 233
5.
May 17 00:03:42 core kernel: Unable to handle kernel paging request at virtual
address c1f5ffe0
May 17 00:03:42 core kernel: current->tss.cr3 = 013eb000, %cr3 = 013eb000
May 17 00:03:42 core kernel: *pde = 00000000
May 17 00:03:42 core kernel: Oops: 0000
May 17 00:03:43 core kernel: CPU: 0
May 17 00:03:43 core kernel: EIP: 0010:[put_cached_page+25/100]
May 17 00:03:43 core kernel: EFLAGS: 00010217
May 17 00:03:43 core kernel: eax: 00380ff9 ebx: c1f5ffc8 ecx: 00000000
edx: c0358000
May 17 00:03:43 core kernel: esi: 00000000 edi: c0de9000 ebp: 00000001
esp: c13dde60
May 17 00:03:43 core kernel: ds: 0018 es: 0018 ss: 0018
May 17 00:03:43 core kernel: Process bash (pid: 75, process nr: 5,
stackpage=c13dd000)
May 17 00:03:43 core kernel: Stack: 73665c73 0000878f 00000002 c0de9000 c01769e3
c0de9000 c0bec790 c01756a3
May 17 00:03:43 core kernel: c0de9000 c12f9644 c0de380c c0cf9c00 c02b14cc
c0de9000 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 with a recursive link, or manually cd through
each directory.
7. See 2. for the test environment
7.1
server:
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux straylight 2.0.36 #1 Sun Dec 20 20:35:25 PST 1998 i586 unknown
Kernel modules 2.1.34
Gnu C 2.7.2.3
Binutils 2.8.1.0.23
Linux C Library 5.4.46
Dynamic linker ldd: version 1.9.9
Linux C++ Library 27.2.8
Linux C++ Library 27.2.8
Procps 2.0.0
Mount 2.8
Net-tools 1.45
Kbd 0.89
Sh-utils 1.16
Modules Loaded ppa ip_masq_ftp
client:
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux core 2.2.9 #1 SMP Fri May 14 06:46:55 PDT 1999 i486 unknown
Kernel modules 2.1.85
Gnu C egcs-2.90.29 980515 (egcs-1.0.3 release)
Binutils 2.8.1.0.23
Linux C Library 5.4.44
Dynamic linker ldd: version 1.9.9
Linux C++ Library 2.8.
Procps 2.0.0
Mount 2.7l
Net-tools 1.51
Kbd 0.94
Sh-utils 1.16
Modules Loaded
7.2
server:
processor : 0
cpu : 586
model : Pentium MMX
vendor_id : GenuineIntel
stepping : 3
fdiv_bug : no
hlt_bug : no
f00f_bug : yes
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic mmx
bogomips : 463.67
processor : 1
cpu : 586
model : Pentium MMX
vendor_id : GenuineIntel
stepping : 3
fdiv_bug : no
hlt_bug : no
f00f_bug : yes
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic mmx
bogomips : 465.31
client:
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : unknown
stepping : unknown
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : -1
wp : yes
flags :
bogomips : 16.54
7.3
server:
ppa 3 0
ip_masq_ftp 1 0
client: N/A
7.4:
server:
Attached devices:
Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: D.17
Type: Direct-Access ANSI SCSI revision: 02
client:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: FUJITSU Model: M2654S-512 Rev: 010P
Type: Direct-Access ANSI SCSI revision: 02
--
Ryan Murray (rmurray@cyberhqz.com, rmurray@glenayre.com)
Engineering Technologist, Glenayre Technologies Inc.
The opinions expressed here are my own.
On 5 Jun 99, "Viral H. Shah" <noeticsolutions@vsnl.com> had questions about Implementing Shares: [snip]> I want ONLY 'nhs' and 'vhs' to have read only access to > '/usr/iso9001/edp' directory. Nobody else should be able to view this > share. How do I implement this? In the smb.conf file I have the > following parameters declared for this share - > > [ISO-EDP] > comment = ISO files for the EDP department > path = /usr/iso9001/edp > valid users = nhs, vhs > public = no > read only = yes > > This works fine when 'nhs' or 'vhs' logs in. However, when 'abc' logs > in, he is able to see the share in the Network Neighborhood even though > he cannot access it. How do I make shares for particular sets of users > visible only to them and nobody else?The last time I played with it, that's exactly the way the "valid users" parameter worked (but I haven't tried 2.x yet), ie, only the valid users could "see" the share in NetHood. I suppose you could set it to "browsable = no" and then map the share to a local drive, but then your valid users wouldn't see it in NetHood either. Should be workable though (even more like Netware, eh?). Steve ************************************************************* Steve Arnold http://www.rain.org/~sarnold Things go better with Linux and King Crimson.
On 5 Jun 99,jim <jed@clipper.net> had questions about Need help with WIN98 printer:> I would like to set up my small home network so that when I want > to print anything from a linux box, it is directed to an HP-500 > on my WIN98 box.Can anyone suggest how to go about doing this? > Copies of a configuration file (smb.conf??) would be appreciated.You don't need samba to do this, just the smbfs support in the kernel (and something like RedHat's printtool to make it easy). If you don't have RedHat, then you should still be able to do it. Make sure your kernel has smbfs support, and check the printing HOWTO for an example of printing to a network printer. (hint: the printer device is /dev/null) I find you learn best by getting your hands dirty, so go to it. Have fun, Steve ************************************************************* Steve Arnold http://www.rain.org/~sarnold "A mime is a terrible thing to waste..." Mel Brooks
On 5 Jun 99, "Robert Aldridge" <RALDRIDG@gulf-states.com> had questions about Newbie question: [snip]> [global] > > # workgroup = NT-Domain-Name or Workgroup-Name > workgroup = LIS > > # server string is the equivalent of the NT Description field > server string = Samba Server > > # This option is important for security. It allows you to restrict > # connections to machines which are on your local network. The > # following example restricts access to two C class networks and > # the "loopback" interface. For more examples of the syntax see > # the smb.conf man page > ; hosts allow = 10.10.50.^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I think you need to set this for your network and the loopback address.> # if you want to automatically load your printer list rather > # than setting them up individually then you'll need this > printcap name = /etc/printcap > load printers = yes > > # It should not be necessary to spell out the print system type unless > # yours is non-standard. Currently supported print systems include: > # bsd, sysv, plp, lprng, aix, hpux, qnx > ; printing = bsd > > # Uncomment this if you want a guest account, you must add this to /etc/passwd > # otherwise the user "nobody" is used > guest account = pcguest^^^^^^^^^^^^^^^^^^^^^^^^^^^^ try setting this to either nobody or ftp. [snip]> # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names > # via DNS nslookups. The built-in default for versions 1.9.17 is yes, > # this has been changed in version 1.9.18 to no. > dns proxy = yes > guest account = pcguest > encrypt passwords = no > password level = 0 > preferred master = no > os level = 0 > null passwords = yes > dead time = 0 > debug level = 0 > domain master = no^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I'm not sure how samba handles multiple definitions of the same parameter, so I'd be a little careful here. ************************************************************* Steve Arnold sarnold@earthling.net http://www.rain.org/~sarnold This message composed of 100% recycled electrons. You should also recycle yourself. Become an organ donor 8-)
On 5 Jun 99, "Robert Aldridge" <RALDRIDG@gulf-states.com> had questions about logging in from NT: [snip]> >From an NT workstation, I open Network Neighborhood. I can see > my Linux server listed (GRASS). When I try to connect to it, it > prompts me for a user name and password. I've tried every > combination of username/password that I can think of, but every > time, I get an error message: > > \\Grass is not accessible. > > The account is not authorized to login from this station.This an artifact of NT. In the winNT.txt file in the samba docs, it states that NT4SP3 trying to connect to samba in user level security will not browse until you have an open connection. Go to a command prompt and map a samba share with the Net Use command (specify your samba username via the command line switch). Then try browsing the samba server in NetHood (it should work fine). Do you have a mapping (in /etc/smbusers or wherever the smbusers file is) for the NT hostname <-> samba username?> I know that my problem is that I'm new to Linux and have never > used Samba, but its a problem none-the-less.Most of the problems are due to poor design, coding, and documentation on the M$ side. And after you've used linux for a while, you'll learn to read the stuff in the /usr/doc tree ;-) Steve ************************************************************* Steve Arnold http://www.rain.org/~sarnold Linux: It's not just for nerds anymore...
On 5 Jun 99, Yah rite <tijian_bbs@hotmail.com> had questions about samba & file ownerships:> Is it at all possible to mount a FAT16/32 filesystem and use > file ownerships on it? I expect not, but figured I should ask the > question to find out for sure.Isn't that what the umsdos filesystem is for? Probably only works with fat16 though. Steve ************************************************ Steve Arnold CLE (Certifiable Linux Evangelist) http://www.rain.org/~sarnold
Wei - I have seen that error message in the past as a symptom of case sensitivity problems. I usually choose the following options in smb.conf in a mixed NT/9x environment: preserve case = yes short preserve case = yes case sensitive = no Then that problem goes away. Thomas Cameron, CNE, MCP, MCT Three-Sixteen Technical Services, Inc. http://www.three-sixteen.com> ------------------------------ > > Date: Thu, 03 Jun 1999 14:04:31 -0400 > From: Wei Yang <weiy@mdarchives.state.md.us> > To: samba@samba.org > Subject: Win95/98 cannot, but NT can! > Message-ID: <4.1.19990603132856.0092bc70@archive5.mdarchives.state.md.us> > > Dear Sir: > > I just installed Samba 2.0.3 in one of our Solaris 2.6 box. One problem I > have is that all of NT 4.0 workstations and servers are fine to connect > with the Samba server but not Window's 95/98. From 95/98, you may see the > Samba server and even map to a drive to the Samba server's share > but cannot > get into it. For example, I can map E: to one of share directories in the > Samba server. Then I can see there are a file called TEST.HTML and a > subdirectory called SRC under the drive E:. But when I double-click this > TEST.HTML file or the SRC subdirectory, I will get an error message says > "The file E:\TEST.HTML doesn't exist" or "The folder E:\SRC > doesn't exist". > Does anyone know how to fix the problem? > > Thanks in advance. > > Wei > > +++++++++++++++++++++++++++++++++ > Wei Yang > Director of Electronic Archives > Maryland State Archives > Email: weiy@mdarchives.state.md.us > Voice: (410)260-6462 Fax: (410)974-2525 > +++++++++++++++++++++++++++++++++ >
Stephen L Arnold wrote:> > > The account is not authorized to login from this station. > > This an artifact of NT. In the winNT.txt file in the samba docs, > it states that NT4SP3 trying to connect to samba in user level > security will not browse until you have an open connection. Go to > a command prompt and map a samba share with the Net Use command > (specify your samba username via the command line switch). Then > try browsing the samba server in NetHood (it should work fine).Not true. Under sp3, MS set the default for NT (and under the redirector update for 95), to not downgrade to plain text passwords if encryption was not supported by the server. This capability is negotiated during the session setup in user mode security. The fix is to either enable encrypted passwords on the samba server (e.g. encrypt passwords = yes), or to use the nt4_plainpassword.reg file included with samba. Cheers, jerry ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
On 5 Jun 99, "Jayson Garrett" <Garrett@mc.edu> had questions about Connecting to 1.9.18p10 from DOS boot diskette:> I'm trying to connect to aSamba 1.9.18p10 share on my HP-UX 10.20 host, > using an MS-DOS boot diskette (well, actually a Windows 95 boot diskette, > but relying on the DOS-style protocol stack, etc.). > > When I issue the same username and password that I use to connect to that > share from my Windows NT client, I get an invalid password message. > > Two things come to mind: is the DOS client sending my username in > uppercase rather than lowercase? Or is the DOS client encrypting the > password, like post-SP3 NT clients do? (I used the EnablePlainTextPassword > option on my NT boxes to take care of that, btw) Or is it something else I > haven't thought of yet? <G>AFAIK, the DOS client sends the password uppercase (like most M$ clients) but does not encrpyt it. I couldn't find much specific to DOS clients in the samba docs, but there are numerous references in the smb.conf man page. Check it out. Steve ************************************************************* Steve Arnold http://www.rain.org/~sarnold "A mime is a terrible thing to waste..." Mel Brooks