linux-kernel - Re: [PATCH 2/2] pnp: add PNP resource range checking function

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] [day] [month] [year] [list]

Message-ID: <20090611133347.1e79b950@jbarnes-g45>
Date:	Thu, 11 Jun 2009 13:33:47 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Eric Anholt <eric@...olt.net>, penberg@...helsinki.fi,
	elendil@...net.nl, linux-kernel@...r.kernel.org, apw@...onical.com,
	colin.king@...onical.com, tim.gardner@...onicalc.com,
	bjorn.helgaas@...com
Subject: Re: [PATCH 2/2] pnp: add PNP resource range checking function

On Tue, 9 Jun 2009 15:09:44 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Mon, 08 Jun 2009 17:53:59 -0700
> Eric Anholt <eric@...olt.net> wrote:
> 
> > On Sat, 2009-06-06 at 10:28 +0300, Pekka Enberg wrote:
> > > Hi Frans,
> > > 
> > > Frans Pop wrote:
> > > >> Add a PNP resource range check function, indicating whether a
> > > >> resource has been assigned to any device.
> > > > 
> > > > Shouldn't this patch come *before* your patch 1/2?
> > > > You now seem to use this function in a commit where it has not
> > > > yet been defined, which could result in build errors during
> > > > bisections.
> > > 
> > > Yes, correct. Sorry about that!
> > > 
> > > 			Pekka
> > 
> > This is already in drm-intel-next
> > 
> 
> Neither patch is in linux-next.  So either a) drm-intel-next contains
> 2.6.31 material or b) your processes broke.

drm-intel-next gets into linux-next by way of drm-next.  Not sure if
Dave has pulled Eric's bits yet though.

> Either way, these patches fix a "serious performance regression".
> They should be merged into 2.6.30 or 2.6.30.x, shouldn't they?

I'm still a little nervous about this, but I won't block it.  Since the
commits don't have stable@...nel.org cc'd I guess Pekka will just have
to send a note to stable when they go upstream.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/