linux-kernel - Re: How to reduce the number of open kernel bugs

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 2 May 2008 13:40:42 -0400
From:	Daniel Hazelton <dhazelton@...er.net>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	"Parag Warudkar" <parag.warudkar@...il.com>,
	"Adrian Bunk" <bunk@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs

On Friday 02 May 2008 13:27:04 Andi Kleen wrote:
> Daniel Hazelton <dhazelton@...er.net> writes:
> >  If the hardware works
> > perfectly in every other OS
>
> It depends. There used to be the famous case (not longer true now) that
> older Linux allocated memory from the top of the memory down and other OS
> generally allocated it the from bottom to up and when some of your top
> memory was broken Linux would often hit problems where other OS did not.

True.

> Also there can be the case when some OS use hardware quite differently
> or different hardware features than other. Standard case for example
> used to be that there were a few platforms where the SMM code had 64bit
> bugs and of course you would only hit them when running a 64bit OS which
> was Linux.

Sadly things like this will continue as long as there is a single OS that has 
more than a 70% market share of the common desktop market.

> A modern OS is a very complicated system with tens of millions of code
> lines and you can't assume they all program the hardware in the same way.
>
> Simple truths are often wrong.

Yes, but if the hardware *ISN'T* broken, then claiming it is and closing out a 
bug is the wrong thing to do. The right thing to do would be to find out why 
the hardware isn't working correctly for the OS/driver combination in 
question and, if possible, fix the driver.

>  - and possibly even previous versions of Linux -
>
> Now that is a more interesting case. But regressions are always taken
> seriously by all maintainers I know.
>

Look to the bug-report posted (cleaned of evidence that would incriminate any 
single person) by (IIRC) Adrian. The guy says "It worked with X and works in 
Windows, but it now fails with message Z."

Maintainer says "Your hardware is broken", closes the bug and then goes on to 
say "If the hardware isn't broken, talk to the people in charge of A and B 
because my code isn't buggy."

That is idiotic and immature.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
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/