linux-kernel - Re: 2.6.24-rc2-mm1

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: <20071115172352.GB24837@linux.intel.com>
Date:	Thu, 15 Nov 2007 09:23:52 -0800
From:	mark gross <mgross@...ux.intel.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Gabriel C <nix.or.die@...glemail.com>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc2-mm1

On Wed, Nov 14, 2007 at 12:40:08PM -0800, Andrew Morton wrote:
> On Wed, 14 Nov 2007 12:29:59 -0800 mark gross <mgross@...ux.intel.com> wrote:
> 
> > > > [  102.366932]  =======================
> > > > [  108.552031] printk: 31 messages suppressed.
> > > 
> > > 
> > > All this BUG / WARNINGS are caused by *-qos* patches. Reverting this 3 patches makes the BUGs go away :
> > > 
> > > latencyc-use-qos-infrastructure.patch
> > > pm-qos-infrastructure-and-interface.patch
> > > pm-qos-infrastructure-and-interface-static-initialization-with-blocking-notifiers.patch
> > > 
> > > 
> > > Gabriel
> > > 
> > > 
> > This looks like the same issue Rafael saw.
> > 
> > Try the patch in the following post:
> > 
> > http://marc.info/?l=linux-kernel&m=119265627228498&w=2
> > 
> 
> Well that's not very good.  _I_ can go fishing in my lkml archives for random
> patches but not everyone is set up to do that.  And the diff to which you
> refer gets 100% rejects against rc2-mm1 anyway.
> 
> Please prepare a tested, changelogged patch against rc2-mm1 asap.  

my bad.  I didn't catch the 24-rc2-mm1 baseline for this issue.  I'll
look at this right way.

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