linux-kernel - Re: [1/2] 2.6.21-rc7: known regressions

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]

Message-ID: <s5hy7kmvr5p.wl%tiwai@suse.de>
Date:	Fri, 20 Apr 2007 20:26:10 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	Adrian Bunk <bunk@...sta.de>, perex@...e.cz,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [1/2] 2.6.21-rc7: known regressions

At Fri, 20 Apr 2007 11:18:07 -0700,
Andrew Morton wrote:
> 
> On Fri, 20 Apr 2007 12:34:18 +0200
> Takashi Iwai <tiwai@...e.de> wrote:
> 
> > Good to hear!  I forgot the patch description and sign-off, so here it
> > is again:
> > 
> > 
> > [PATCH] ALSA: intel8x0 - Fix Oops in crash kernel
> > 
> > When intel8x0 driver is loaded in the crash kernel, it gets Oops
> > occasionally.  This is because the irq handler gets called before
> > the proper hardware initialization.  Now defer it after
> > snd_intel8x0_chip_init().
> 
> Neat, thanks.
> 
> Do we think this is safe enough and important enough for 2.6.21?
> And if so, do you want me to merge it?

It should be safe (as I already merged ALSA tree for 2.6.22), but I'd
like to test the following before merging 2.6.21:
- suspend/resume works
- no severe problem even if request_irq() fails
I'll check this in this weekend, so let's hold on.


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