[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0904061501470.7443@localhost.localdomain>
Date: Mon, 6 Apr 2009 15:05:07 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Lin Ming <ming.m.lin@...el.com>, Nick Piggin <npiggin@...e.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: [Bug #12809] iozone regression with 2.6.29-rc6
On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28. Please verify if it still should be listed and let me know
> (either way).
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12809
Hmm. I applied the commit that should fix it, but I applied it _after_
2.6.29. I was too scared to apply it late in the -rc and quite frankly
I'm not sure we should necessarily back-port it.
So I'm hoping that we can close it as "fixed", even though 2.6.29 will
have that particular regression - for those particular machines. It is,
after all, just a "where do we draw the line" kind of issue.
But I won't close it myself, and I leave it to others to argue whether it
really maybe should be back-ported after all.
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/
Powered by blists - more mailing lists