Bug 880204 - smbd segfault while trying to delete file
Summary: smbd segfault while trying to delete file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-26 13:44 UTC by Jeff Layton
Modified: 2014-06-18 07:42 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 00:28:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
corefile from delete attempt (1.06 MB, application/octet-stream)
2012-11-26 13:45 UTC, Jeff Layton
no flags Details

Description Jeff Layton 2012-11-26 13:44:38 UTC
I had a share mounted from a Linux cifs client and then tried to delete a file. It segfaulted and left a corefile in the share directory.

Coredump attached. Here's a summary from gdb:

Reading symbols from /usr/sbin/smbd...Reading symbols from /usr/lib/debug/usr/sbin/smbd.debug...done.
done.
BFD: Warning: /scratch/./core.22165 is truncated: expected core file size >= 21536768, found: 16945152.
[New LWP 22165]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Failed to read a valid object file image from memory.
Core was generated by `/usr/sbin/smbd'.
Program terminated with signal 11, Segmentation fault.
#0  _IO_vfprintf_internal (s=s@entry=0x7fff4a2e73b0, format=format@entry=0x7f54e4f92124 ":%s", ap=ap@entry=0x7fff4a2e7538)
    at vfprintf.c:232
232	  int save_errno = errno;

...the stack is HUGE (>1000 stack frames), so it looks like this may be some sort of recursion problem? In any case, this machine is running:

samba-3.6.9-96.fc17.1.x86_64

Comment 1 Jeff Layton 2012-11-26 13:45:48 UTC
Created attachment 651974 [details]
corefile from delete attempt

Comment 2 Andreas Schneider 2013-01-30 10:00:58 UTC
Can you still reproduce this and get more frames. There is no vfprintf.c in Samba.

Comment 3 Fedora End Of Life 2013-07-03 22:30:32 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2013-08-01 00:28:18 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.