linux-kernel - Re: [PATCH] PCI: boot parameter to avoid expansion ROM memory allocation

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: <200805201316.33882.jbarnes@virtuousgeek.org>
Date:	Tue, 20 May 2008 13:16:33 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Gary Hade <garyhade@...ibm.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH] PCI: boot parameter to avoid expansion ROM memory allocation

On Tuesday, May 20, 2008 1:00 pm Gary Hade wrote:
> On Tue, May 20, 2008 at 10:57:49AM -0700, Jesse Barnes wrote:
> > On Wednesday, May 14, 2008 9:20 am Gary Hade wrote:
> > > > Correct, not a perfect solution but better than we have right now.
> > >
> > > ...but don't let this comment make you think that I am not in
> > > favor of something like you are suggesting.  I am interested
> > > in getting the 'pci=norom' change into mainline quickly but it
> > > is obviously less than ideal for the long term.
> > >
> > > Jesse, any idea how many different devices absolutely need
> > > memory allocated for their expansion ROMs?
> >
> > Unless there's a ton of demand, I'd rather go with the norom option, but
> > either way, I'd like to push the fix early in the 2.6.27 cycle rather
> > than trying to get it into 2.6.26 at the last minute...
>
> This is fine.  I would also like to see the pci=norom option
> added as-is with the thought that we may improve later by either
> modifying pci=norom to exclude devices that need memory mapped
> to their expansion ROMs or by adding another option (pci=minrom ?)
> that would do the same thing.
>
> > So assuming you're ok with your last patch, I'll stuff it into
> > linux-next.
>
> Works for me.  Thanks.

Ok, just pushed the norom patch to linux-next.  I'll test it out, but it would 
be good if you could try the tree out out on one of the problem machines too.

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