Bug 14567 - smbclient in 4.13.X tree segfaults using tarmode
Summary: smbclient in 4.13.X tree segfaults using tarmode
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: 4.13.2
Hardware: x64 All
: P5 normal (vote)
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
Depends on:
Reported: 2020-11-04 16:10 UTC by Brent
Modified: 2020-11-09 19:10 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Brent 2020-11-04 16:10:32 UTC
Steps to re-create by trying to use smbclient in tarmode to backup a SMB share.  This will segfault even if using this command on the linux host if it is set to run with SMB shares.  Substitute "server" with "localhost", username, and share name if it is easier to test.

1)  touch /tmp/current-date
2)  /usr/bin/smbclient \\\\server\\c\$ -U Administrator -E -d 1 -c tarmode\ full -TcN /tmp/current-time - /TEMP
3)  Type in the remote server Administrator password
4)  Witness a segfault

I've complied version 4.13.1 and 4.13.2 from source and both will segfault when running the smbclient command.  Going back to 4.12.9 source code works as expected.

Running Fedora 33, kernel is 5.8.17-300.
Comment 1 Jeremy Allison 2020-11-05 19:10:01 UTC
I can't reproduce this with current master. It may have already been fixed by Volker's recent libsmbclient/smbclient changes.

Can you either try current master, of upload a full gdb stack backtrace.

Thanks !
Comment 2 Brent 2020-11-09 19:09:05 UTC
After debugging this issue and running some traces, I've deduced the issue.

I found a 32-bit libwbclient somehow installed on my system.  I don't know how it came to be installed.  I removed that library and now smbclient no longer segfaults.  

This appears to be an issue with how Fedora delivered some updates.

You may close this issue.