Bug Reporting: Difference between revisions

From SambaWiki
(add text on reporting security bugs correctly)
(suggest to include version number)
Line 6: Line 6:


* Report the problem in the Samba bug tracking system: https://bugzilla.samba.org/
* Report the problem in the Samba bug tracking system: https://bugzilla.samba.org/

* Always include the Samba version number in your bug reports!


{{Imbox
{{Imbox

Revision as of 22:47, 25 February 2020

Samba

  • Always include the Samba version number in your bug reports!

cifs.ko

If you run into problems with the SMB client in the Linux kernel (cifs.ko, mount.cifs) don't hesitate to report it.

For the kernel client things are a bit more complex. There are 2 bug tracking systems which you should look at to see if your problem has already been reported:

You can also ask questions on the linux-cifs mailing-list (linux-cifs@vger.kernel.org ) (web archive here).

If you report a bug, a network capture and a kernel console log output is always helpful.

    # make the kernel as verbose as possible
    echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
    echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
    echo 1 > /proc/fs/cifs/cifsFYI
    echo 1 > /sys/module/dns_resolver/parameters/debug
    
    # get kernel output + network trace
    dmesg --clear
    tcpdump -s 0 -w trace.pcap & pid=$!
    sleep 3
    mount.cifs ....cd ... ls.. etc.. (the thing that fails)
    sleep 3
    kill $pid
    dmesg > trace.log

This should produce a trace.pcap and a trace.log file.

Be sure to mention your kernel version, server software and version.

Additional information on debugging the CIFS/SMB3 kernel client can be found at: https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting