Bug 8251 - smbtorture triggers 'panic action' script at NTTRANSSCAN test
Summary: smbtorture triggers 'panic action' script at NTTRANSSCAN test
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: Client Tools (show other bugs)
Version: 3.5.4
Hardware: x64 Linux
: P5 minor
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
Depends on:
Reported: 2011-06-21 22:47 UTC by Michael Eitelwein
Modified: 2011-06-26 16:47 UTC (History)
0 users

See Also:

log.smbd (3.90 KB, text/plain)
2011-06-21 22:50 UTC, Michael Eitelwein
no flags Details
smbtorture output (245.25 KB, text/plain)
2011-06-21 22:51 UTC, Michael Eitelwein
no flags Details
Client log (36.12 KB, text/plain)
2011-06-26 15:47 UTC, Michael Eitelwein
no flags Details
smbd log (14.17 KB, text/plain)
2011-06-26 15:47 UTC, Michael Eitelwein
no flags Details
smbtorture output (1.62 KB, text/plain)
2011-06-26 15:48 UTC, Michael Eitelwein
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Eitelwein 2011-06-21 22:47:04 UTC
I filed all info in ubuntu launchpad


Please let me know if I should post all info here again,
Comment 1 Michael Eitelwein 2011-06-21 22:50:50 UTC
Created attachment 6602 [details]
Comment 2 Michael Eitelwein 2011-06-21 22:51:24 UTC
Created attachment 6603 [details]
smbtorture output
Comment 3 Michael Eitelwein 2011-06-21 22:52:37 UTC
This is the email that notified me about the panic action:

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 11435 (/usr/bin/smbtorture).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred.  The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries.  Then submit the provided information as a bug report to
Ubuntu by visiting this link:

[Thread debugging using libthread_db enabled]
0x00007f104b738dee in waitpid () from /lib/libc.so.6
#0  0x00007f104b738dee in waitpid () from /lib/libc.so.6
#1  0x00007f104b6d0a79 in ?? () from /lib/libc.so.6
#2  0x00007f104d9dd1f4 in smb_panic ()
#3  0x00007f104d9ca515 in push_ucs2 ()
#4  0x00007f104d8fa768 in clistr_push_fn ()
#5  0x00007f104d8b07cc in ?? ()
#6  0x00007f104d8b0a1e in torture_nttrans_scan ()
#7  0x00007f104d8aa1da in ?? ()
#8  0x00007f104d8aa0c5 in ?? ()
#9  0x00007f104d8aa91f in main ()
A debugging session is active.

        Inferior 1 [process 11435] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Comment 4 Jeremy Allison 2011-06-21 23:43:17 UTC
Can you try and reproduce this with the latest Samba 3.5.9 please ?
Comment 5 Michael Eitelwein 2011-06-22 23:10:25 UTC
I updated to 3.5.8 (the last stable ubuntu release of samba in natty) and ran into the same problem:

starting nttrans scan test
Scanning op=0
Pushing string of 'unlimited' length into non-SMB buffer!
PANIC (pid 4501): push_ucs2 - invalid dest_len of -1
BACKTRACE: 10 stack frames:
 #0 smbtorture(log_stack_trace+0x1a) [0x7feb8f1d9a3a]
 #1 smbtorture(smb_panic+0x1f) [0x7feb8f1d9aff]
 #2 smbtorture(+0x1a3995) [0x7feb8f1c6995]
 #3 smbtorture(clistr_push_fn+0x68) [0x7feb8f0f6d28]
 #4 smbtorture(+0x8a54c) [0x7feb8f0ad54c]
 #5 smbtorture(torture_nttrans_scan+0xae) [0x7feb8f0add9e]
 #6 smbtorture(+0x7d132) [0x7feb8f0a0132]
 #7 smbtorture(main+0x2e9) [0x7feb8f0ac069]
 #8 /lib/libc.so.6(__libc_start_main+0xfe) [0x7feb8cea9d8e]
 #9 smbtorture(+0x77219) [0x7feb8f09a219]
smb_panic(): calling panic action [/usr/share/samba/panic-action 4501]
smb_panic(): action returned status 0
Can not dump core: corepath not set up

I won't have the time to set up a test machine with a 3.5.9 release the next weeks. Is there another way to narrow down the bug? Especially as it might be connected to the instability of seahorse on CIFS shares, which I see as a serious problem.
Comment 6 Volker Lendecke 2011-06-23 20:36:50 UTC
That seems to be a crash in the smbtorture binary. That's not really a show-stopper for us, the NTTRANSSCAN test is pretty bogus these days. I very much doubt that this has anything to do with an smbd instability. The log.smbd does not show any hint at a problem. It seems that you have some "log file =" setting in your smb.conf file, you did not upload the required client-specific log file.
Comment 7 Michael Eitelwein 2011-06-26 15:47:04 UTC
Created attachment 6627 [details]
Client log

Client log when smbtorture crashes
Comment 8 Michael Eitelwein 2011-06-26 15:47:48 UTC
Created attachment 6628 [details]
smbd log
Comment 9 Michael Eitelwein 2011-06-26 15:48:39 UTC
Created attachment 6629 [details]
smbtorture output

I generated the log files again, as the client log was missing.
Comment 10 Volker Lendecke 2011-06-26 16:47:54 UTC
As I said, this is smbtorture3 crashing in a very minor test. Lowering priority.