linux-kernel - Re: [PATCH] [1/12] x86: Work around mmio config space quirk on AMD Fam10h

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:	Sun, 12 Aug 2007 12:15:26 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andi Kleen <ak@...e.de>
cc:	dean@...tic.org, patches@...-64.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [1/12] x86: Work around mmio config space quirk on AMD
 Fam10h

On Sun, 12 Aug 2007, Andi Kleen wrote:
> >
> > Damn you, Andi.
> 
> Thanks for the kind words.

Should I be impressed by the fact that 16% of your patches caused bootup 
problems, when we're really close to a -rc3, and *long* past the point 
where we want to address regressions rather than cause them?

I simply want you to be more careful.  *Much* more careful. As it is, I 
end up always being afraid of merging your patch-series (and yes, I should 
have found this even earlier when reading through the diff rather than 
after I had already applied it, but I didn't, and we had a broken kernel 
for a few hours as a result. I didn't see any bug-reports about this one, 
so hopefully nobody noticed, but it still grates me).

Bugs happen, but (a) they should happen during the merge window, not when 
we're in stabilization phase and (b) the percentages here were just not 
very good.

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