linux-kernel - Re: 2.6.25-rc2: Reported regressions from 2.6.24

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, 18 Feb 2008 12:24:53 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.25-rc2: Reported regressions from 2.6.24

On Monday, 18 of February 2008, Arjan van de Ven wrote:
> On Sun, 17 Feb 2008 23:03:59 +0100
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> 
> > [This is a bit late, for which I'm sorry, but I waited for things to
> > calm down a bit, to have something less of a moving target.
> > 
> > Now, following an Ingo's advice, the list has been generated directly
> > out of the Bugzilla entries used for tracking the bugs.  I'm going to
> > release the script used for generating the list, so that it can be
> > recreated by anyone on the fly.]
> > 
> > This message contains a list of some regressions from 2.6.24 reported
> > since 2.6.25-rc1 was released, for which there are no fixes in the
> > mainline I know of.  If any of them have been fixed already, please
> > let me know.
> > 
> > If you know of any other unresolved regressions from 2.6.24, please
> > let me know either and I'll add them to the list.  Also, please let
> > me know if any of the entries below are invalid.
> 
> 
> question: can we please list the last known good version for each entry?
> Since these are all regressions (right?) that information ought to be available 
> and usually helps down in narrowing causes..

Well, this usually is only obvious for the cases in which the "guilty" commit
has been identified and that information is already provided in the Bugzilla
entries.

I can add a "Caused-By" tag so that it gets listed, if that helps.

Thanks,
Rafael
--
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/