Bug 4137 - PANIC in some situations with "Only user = Yes"
PANIC in some situations with "Only user = Yes"
Product: Samba 3.0
Classification: Unclassified
Component: File Services
All Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-09-30 01:32 UTC by Christian Perrier
Modified: 2006-09-30 15:29 UTC (History)
1 user (show)

See Also:

smb.conf file which triggers the PANIC (305 bytes, text/plain)
2006-09-30 01:33 UTC, Christian Perrier
no flags Details
level 10 log of the panic (160.40 KB, application/x-gzip)
2006-09-30 01:34 UTC, Christian Perrier
no flags Details
proposed patch (540 bytes, patch)
2006-09-30 04:45 UTC, Volker Lendecke
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Perrier 2006-09-30 01:32:23 UTC
This bug is closely described in http://bugs.debian.org/388282

We needed time to narrow it with our user. It finally turned out that smbd panics in his setup (smb.conf file attached) when he add the deprecated option "Only user = Yes" in his [homes] section. A level 10 debug log is attached also
Comment 1 Christian Perrier 2006-09-30 01:33:21 UTC
Created attachment 2166 [details]
smb.conf file which triggers the PANIC
Comment 2 Christian Perrier 2006-09-30 01:34:57 UTC
Created attachment 2167 [details]
level 10 log of the panic
Comment 3 Volker Lendecke 2006-09-30 04:45:25 UTC
Created attachment 2168 [details]
proposed patch

This panic is actually correct. First "only user" is deprecated, I think that y\
ou wanted to say 'valid users = %S'. Then, the manpage for "only user" says

Enabling this parameter will force the
server to only user the login names from  the  user
list and is only really useful in shave level security.

As you have user level security, "only user" does not really make sense. If you\
 _want_ to use it, you also need the "username = " option in your share definit\

The attached patch turns this panic into a debug level 0 message.

Comment 4 Volker Lendecke 2006-09-30 04:46:34 UTC
Fixed with r19010
Comment 5 Thomas Bork 2006-09-30 15:29:05 UTC
(In reply to comment #4)
> Fixed with r19010

But only in SAMBA_3_0 and not in SAMBA_3_0_23