Bug 8202 - Any Windows machine writes to a Samba share on a Fedora machine it will crash the Fedora operating system every time
Summary: Any Windows machine writes to a Samba share on a Fedora machine it will crash...
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.5.8
Hardware: x86 Linux
: P5 critical
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-02 14:56 UTC by b2566996
Modified: 2011-06-08 08:05 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description b2566996 2011-06-02 14:56:20 UTC 
* Any Windows machine writes to a Samba share on a Fedora machine it will crash the Fedora operating system every time.
* The Windows machine can consistently read with no trouble.
* An Ubuntu machine can read and write to the same share and as the same user without incident.
* It was working fine for nearly a year and stopped recently without modification to the system or config files except for updates.
* Nothing gets logged in /var/log/messages.  It just cuts off until hardboot.
*  The only thing logged in /var/log/samba/* is many instances of this: "[2011/05/29 17:01:52.267773,  0] smbd/nttrans.c:2271(call_nt_transact_ioctl)   call_nt_transact_ioctl(0x900eb): Currently not implemented" but it does not correlate with the times the machine crashes.
* The problem persists when writing to /dev/shm via samba to rule out hard disk.
* Uninstalled and reinstalled Samba.
* Memtest checked out OK.
* Disabled IPv6 on Windows.
* Samba version: 3.5.8-76.fc14.
* Tried kernels: 2.6.35.11-83.fc14.i686  2.6.35.13-91.fc14.i686 and 2.6.35.12-90.fc14.i686
Comment 1 Volker Lendecke 2011-06-03 10:06:48 UTC 
Weird. If it really crashes the box hard, I'd say this is not a Samba bug.
Comment 2 Volker Lendecke 2011-06-06 08:59:41 UTC 
Günther, have you seen this before in Fedora?

Volker
Comment 3 b3042911 2011-06-08 02:29:09 UTC 
It turned out to be a bad NIC. Added in a second NIC, gave it the original IP, and told samba to look at the new interface... So far everything seems to be working. :/ Thanks for checking into it.
Comment 4 Volker Lendecke 2011-06-08 08:05:07 UTC 
Please re-open if it turns out to be more Samba-specific