Hi, cifs.ko (and cifs-utils) bugs are reported in 2 different places. You have the samba.org bugzilla and kernel.org bugzilla. I've documented this and added debugging instructions on the samba wiki couple of months ago [1]. This situation is not ideal. We can have the same bug reported in 2 places with no way of marking duplicates or making cross-references. Additionnaly, the samba.org bz has IMO a couple of issues: * I was told only Samba Team members can edit bug status/info/etc. Which is a pretty small subset of people, among which an even smaller subset of people actually work on cifs.ko. * Bug metadata is related to samba more than the kernel. * Due to spam, the samba.org bz requires a manual admin validation to activate new accounts so opening bugs for new people is a bit annoying. On kernel.org bz I think the registration process is a simple email verification and AFAIK the subset of people who can edit bug status/info/etc is easily manageable by the subsystem maintainer. Given these issues I think we should completely move to kernel.org bugzilla. Possible plans (or variations of) would be: a) import samba.org bugs in kernel.org and remove the cifs.ko section from samba bz b) block adding bugs in samba bz and use kernel bz for new bugs For b) we could also possibly move the old bugs to the new bz slowly over time. Let me know what you think. Cheers, 1: https://wiki.samba.org/index.php/Bug_Reporting#cifs.ko -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
