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  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:	Tue, 5 Oct 2010 00:40:59 +0200
From:	"Rafael J. Wysocki" <>
To:	Anisse Astier <>,
	"Greg Kroah-Hartman" <>
Cc:	Linux Kernel Mailing List <>,
	Kernel Testers List <>,
	Maciej Rutecki <>,
	Florian Mickler <>,
	Eric Anholt <>,
	Tim Gardner <>,
	Daniel Vetter <>,
	Andrew Morton <>,
	Jesse Barnes <>,
	Chris Wilson <>
Subject: Re: [Bug #16891] Kernel panic while loading intel module during boot

On Monday, October 04, 2010, Anisse Astier wrote:
> On Mon, Oct 4, 2010 at 9:42 PM, Rafael J. Wysocki <> wrote:
> >> I'll provide this patch here in the meantime in case anyone is interested.
> >
> > Thanks for the update and the patch.
> >
> > Well, I wonder who's going to merge it?
> >
> I'm not sure is going to be merged because most of this code has been
> re-written and has been sitting in drm-intel-next for a few weeks now.
> This (welcome) rewrite will likely be merged in 2.6.37 (but I can't
> speak for Chris).
> This is a port of this patch:
> , but on completely different code.
> Also this patch is new and didn't see much testing (I tested on 4
> different Intel GPUs, belonging only to 2 different families); if it's
> not merged for 2.6.36, it won't be for 2.6.37 (the new code will land
> first). If that happens, it might not meet conditions to be accepted
> in -stable (being in linus' tree first).

It's a panic fix, so I think it is -stable material anyway.  Greg?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists