Bug 162958 - Removing [homes] section of the smb.conf causes a segfault.
Removing [homes] section of the smb.conf causes a segfault.
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: samba (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Simo Sorce
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-07-11 16:42 EDT by Johnny Hughes
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-28 16:08:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Samba Project 1983 None None None Never

  None (edit)
Description Johnny Hughes 2005-07-11 16:42:38 EDT
Description of problem:  Removing [homes] section of the smb.conf causes a segfault.

Version-Release number of selected component (if applicable):  samba-3.0.10-1.4E

How reproducible:  Always

This bug describes the problem.  It is supposedly fixed in samba-3.0.11.

Comment 1 RHEL Product and Program Management 2006-08-18 13:33:57 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 2 Nalin Dahyabhai 2006-08-29 14:18:26 EDT
Can you provide some more detail on how to trigger the segfault?  It's not
immediately obvious to me how this can be done, as removing the section and
either restarting or reloading the 'smb' service didn't cause any problems on my
tests setup, even for subsequent connection requests.
Comment 4 Kevin Krafthefer 2007-03-28 16:08:25 EDT
The requested information never came in for a resolution to be arrived at. We
are unable to reproduce here at Red Hat. Please reopen this bug if you can
provide the requested information.

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