linux-kernel - Re: [git pull] PCI fixes

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]

Date:	Fri, 24 Jun 2011 09:11:48 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ram Pai <linuxram@...ibm.com>, yinghai@...nel.org
Subject: Re: [git pull] PCI fixes

On Fri, 24 Jun 2011 09:07:46 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Fri, Jun 24, 2011 at 8:53 AM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> >
> > Some discussion was under "PCI: fix cardbus and sriov regressions",
> > which includes a patchset as well. Oliver Hartkopp's problem is the one
> > that worries me most. The SR-IOV issue is really a BIOS bug and
> > unlikely to affect many people anyway (SR-IOV is really a big server
> > feature).
> 
> Ouch. That is much bigger than I was hoping for. Especially that
> second patch doesn't look like some -rc5 candidate.
> 
> And the fact that Oliver then at the end shows an impossibly aligned
> resource shows that it clearly isn't even remotely correct even AFTER
> the patches, so that doesn't make me get all warm and fuzzy either.
> 
> So I guess we should just revert again.

How about a boot param?  We've done similar things for _CRS, and it
might give Yinghai and Ram some more flexibility in improving our
dynamic resource allocation before enabling it again (if ever).

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