[Bugs] [Bug 1716440] New: SMBD thread panics when connected to from OS X machine
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jun 3 14:06:06 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1716440
Bug ID: 1716440
Summary: SMBD thread panics when connected to from OS X machine
Product: GlusterFS
Version: 6
Hardware: x86_64
OS: Linux
Status: NEW
Component: libgfapi
Severity: high
Assignee: bugs at gluster.org
Reporter: ryan at magenta.tv
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Created attachment 1576680
--> https://bugzilla.redhat.com/attachment.cgi?id=1576680&action=edit
Debug level 10 log of client connection when panic occurs
Description of problem:
When connecting to a share, the SMB thread for that client panics and
constantly restarts. This was tested from a machine running OS X 10.14.4. I've
not been able to test from a windows machine yet.
Version-Release number of selected component (if applicable):
Gluster = 6.1
Samba = 4.9.6
How reproducible:
Every time
SMB configuration:
[global]
security = user
netbios name = NAS01
clustering = no
server signing = no
max log size = 10000
log file = /var/log/samba/log-%M-test.smbd
logging = file
log level = 10
passdb backend = tdbsam
guest account = nobody
map to guest = bad user
force directory mode = 0777
force create mode = 0777
create mask = 0777
directory mask = 0777
store dos attributes = yes
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
glusterfs:volfile_server = localhost
kernel share modes = No
[VFS]
vfs objects = glusterfs
glusterfs:volume = mcv02
path = /
read only = no
guest ok = yes
Steps to Reproduce:
1. Use provided SMB configuration
2. Restart SMB service
3. Connect to share from client using guest user
4. Tail client logs on server to see panics
Actual results:
SMB thread panics and restarts
Expected results:
Client connects and SMB thread doesn't panic
Additional info:
Tested without Gluster VFS and used the FUSE mount point instead and system did
not panic
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list