[Samba] Fwd: smbclient Version 4.13.2 Crashes on Fedora 33

[Noel Power]

Resending to the list as it got rejected because I sent from wrong email
address



-------- Forwarded Message --------
Subject: 	Re: [Samba] smbclient Version 4.13.2 Crashes on Fedora 33
Date: 	Thu, 26 Nov 2020 17:12:29 +0000
From: 	Noel Power <nopower at suse.de>
Reply-To: 	noel.power at suse.com
To: 	tkevans at tkevans.com, Jeremy Allison <jra at samba.org>
CC: 	samba at lists.samba.org



I have reproduced this locally (while using tarmode myself) so I'll look
at it

Noel

On 24/11/2020 20:10, Tim Evans via samba wrote:
> On 11/24/20 1:03 PM, Jeremy Allison wrote:
>> On Tue, Nov 24, 2020 at 10:30:11AM -0500, Tim Evans via samba wrote:
>>> Have been working this on the BackupPC users and Fedora mailing
>>> lists, but it's looking more like a general problem in Samba
>>> utility, 'smbclient.'
>>>
>>> BackupPC is a backup server package that uses Samba, rsync, and
>>> other protocols to backup clients, including Windows PC's.
>>> Basically, it runs a command like this for a SMB backup of a PC:
>>>
>>> /usr/bin/smbclient \\\\new-pelican\\C\$ -U backup -E -d 2 -c
>>> tarmode\ full -Tc -
>>>
>>> Output is piped to BackupPC utilities that unpack and index the
>>> backup, and do other housekeeping
>>>
>>> My backups have consistently failed since my upgrade to F33 (were
>>> working without problems for years before, and most recently on F32).
>>>
>>> Looking closely, it appears 'smbclient' is crashing after passing
>>> exactly 47 files. (BackupPC then quits after data stops coming in.)
>>>
>>> I've run this command at the command-line; it runs for a few seconds
>>> then reports a core dump. Gnome shell then prompted me to file a
>>> Fedora bugzilla, which I have done.
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1900232 "[abrt]
>>> samba-client: remove_do_list_queue_head(): smbclient killed by
>>> SIGSEGV")
>>>
>>> (I can't seem to make this bug report publicly readable...)
>>>
>>> Anybody have further suggestions, please?
>>
>> Can you log a bug at bugzilla.samba.org and upload a
>> gdb stack backtrace please ?
>
> I don't have a bugzilla account there, and have gone through the
> required process to ask for one, just to post one report. Don't know
> how long this takes.
>
>