linux-kernel - Re: [PATCH] module_author: don't advice putting in an email address

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070512071455.GH7984@stusta.de>
Date:	Sat, 12 May 2007 09:14:55 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"John Anthony Kazos Jr." <jakj@...-k-j.com>,
	Rene Herman <rene.herman@...il.com>,
	Rusty Russell <rusty@...tcorp.com.au>, randy.dunlap@...cle.com,
	akpm@...ux-foundation.org, rpjday@...dspring.com,
	marcel@...tmann.org, hch@...radead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module_author: don't advice putting in an email address

On Fri, May 11, 2007 at 10:35:00PM +0100, Alan Cox wrote:
> > This still wouldn't solve the following problems:
> > - I doubt it will be kept up to date for all > 2800 modules in the kernel
> > - the 3 year old kernel of your distribution would contain 3 year old
> >   maintainership information
> > - maintainers sometimes disappear
> 
> Maintainers sometimes DON'T disappear ....

No disagreement about that.

But things like disappearing maintainers, unmaintained code, and 
maintainership that is at most informal (e.g. currently the floppy 
driver) are real-life problems that do occur in several cases.

> > The default for "bug and defect reports" should be for all modules (as 
> > well as for non-modular code) from ftp.kernel.org kernels either 
> > linux-kernel or the kernel Bugzilla. [1]
> 
> If users put it in the kernel bugzilla its gets lost because most of the
> bugzilla isn't set up to route bugs to maintainers. In the unlikely event

Bugzilla is actually setup to route bugs of the maintainer, this is 
currently implemented through the Bugzilla feature "Andrew"...

> it arrives there or it gets posted to linux-kernel the only reply is
> "report it to your distributor"
> 
> > For distribution kernels (which are what most users are using), the
> > default for "bug and defect reports" should be the distribution support.
> 
> I'd prefer not. I get reports from people about drivers that got "lost"
> by vendors, regularly. Nor am I pointing fingers at specific vendors here,
> last month I sorted out a two year old "lost in Red Hat Bugzilla" kernel
> bug for example.

How many maintainers want to get bug reports against the kernel 2.6.9 
shipped with RHEL 4?

> Alan

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/