Bug Reporting: Difference between revisions
From SambaWiki
Mmuehlfeld (talk | contribs) (Rewrote page. Added information how to report doc bugs.) |
(emphasize how to report sec issues) |
||
(6 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
= |
== Samba == |
||
* Report all suspected [https://www.samba.org/samba/security/ Security issues] to '''security@samba.org''' to allow us to follow our [[Samba_Security_Process|Security Process]]. |
|||
To report a bug in Samba: |
|||
* Read the instructions: https://www.samba.org/~asn/reporting_samba_bugs.txt |
* Read the instructions: https://www.samba.org/~asn/reporting_samba_bugs.txt |
||
* 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 |
||
Line 12: | Line 14: | ||
}} |
}} |
||
== 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. |
|||
{{Imbox |
|||
| type = important |
|||
| text = Similarly, please report all '''security''' issues or defects in the kernel client or its userspace tools (cifs-utils, mount.cifs, ...) to '''security@samba.org''' and never on IRC, public mailing lists or in Bugzilla. |
|||
}} |
|||
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: |
|||
* [https://bugzilla.samba.org/buglist.cgi?component=kernel%20fs&list_id=14383&product=CifsVFS&resolution=--- Samba bugzilla kernel section] |
|||
* [https://bugzilla.kernel.org/buglist.cgi?component=CIFS&product=File%20System&resolution=--- Linux bugzilla cifs section] |
|||
You can also ask questions on the [http://vger.kernel.org/vger-lists.html#linux-cifs linux-cifs mailing-list] (linux-cifs@vger.kernel.org ) ([https://marc.info/?l=linux-cifs&r=1&w=3 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. |
|||
= Reporting a Bug in the Samba Documentation = |
|||
Be sure to mention your '''kernel version''', '''server software and version'''. |
|||
To report a bug in the Samba documentation, such as the Wiki or man pages: |
|||
Additional information on debugging the CIFS/SMB3 kernel client can be found at: |
|||
* Log in to the Samba bug tracking system: https://bugzilla.samba.org/ |
|||
https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting |
|||
* Select the <code>Samba 4.1 and newer</code> product. |
|||
* Select the <code>Documentation</code> component. |
|||
* Fill the fields and include the following details in the bug description: |
|||
:* URL or name of the man page |
|||
:* Detailed information what is wrong |
Latest revision as of 15:57, 27 July 2020
Samba
- Report all suspected Security issues to security@samba.org to allow us to follow our Security Process.
- Read the instructions: https://www.samba.org/~asn/reporting_samba_bugs.txt
- Report the problem in the Samba bug tracking system: https://bugzilla.samba.org/
- Always include the Samba version number in your bug reports!
Before you report a bug, verify that you are running a maintained version of Samba and update, if necessary. |
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.
Similarly, please report all security issues or defects in the kernel client or its userspace tools (cifs-utils, mount.cifs, ...) to security@samba.org and never on IRC, public mailing lists or in Bugzilla. |
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