linux-kernel - Re: [patch] x86, voyager: fix ioremap

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]

Date:	Mon, 28 Apr 2008 13:50:57 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	alan@...rguk.ukuu.org.uk, James.Bottomley@...senPartnership.com,
	tglx@...utronix.de, linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

* David Miller <davem@...emloft.net> wrote:

> > So review them. Your comments strike me as the pot calling the 
> > kettle black given the way the network people like to live on their 
> > own mailing list.
> 
> Oh contraire.  Because we networking folks use a seperate mailing list 
> with a lower signal to noise ratio than lkml, and as a result more 
> specialization, more patches get more review by more specialists.

well, then lets go back to the very basis of this whole ... box match.
:) It was about a broken networking patch that i stumbled upon
(unwillingly, via testing), which commit was _not_ posted on netdev and 
_not_ posted on lkml:

   http://lkml.org/lkml/2008/4/19/51

I simply hit a (trivial) regression in the networking code, but i simply 
found no existing discussion of the suspect patch (commit 5e8fbe2a).

the development process is an integral part of the source code of this 
OS and not a private matter of developers or maintainers. It is not a 
religion and it is not taboo to criticise it, it is a crutial part of 
our technology. So i will continue to criticise the development process 
in the future too when i think it has aspects that hurts us. [and will 
try to address all incoming criticism as well.]

> You might want to know that linux-next mainly exists because of how 
> much of this has been going on over the past half year or so.

the problem is that linux-next alone would not have helped much in this 
specific matter. For example the softlockup warnings annoyance you 
reported would have triggered immediately had you booted your Sparc64 
box with linux-next or -mm even just _once_ :-)

But the same holds for me: had i ran linux-next i could have reported 
some of the networking regressions sooner.

So how about making mutual use of linux-next and 'promise' to each other 
to at least minimally build/boot the integrated tree, or at least 
promise to not complain too loudly about bugs that could have been found 
and reported there via reasonable mutual testing of linux-next? Does 
that sound reasonable?

	Ingo
--
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/