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]

Message-ID: <BANLkTime_w_RLqU2dZV4zx9SEZaNTQoMNQ@mail.gmail.com>
Date:	Fri, 24 Jun 2011 08:38:07 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] PCI fixes

On Thu, Jun 23, 2011 at 1:37 PM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
>
> Just a few minor fixes.  We have one open issue with the resource
> re-allocation code that was re-added.  Ram has a fix but I'm concerned
> it will introduce other regressions.  So at this point we have a few
> options:
>  - revert the bridge resource re-allocation code (again)
>  - hide the re-allocation code behind a new kernel option (and not
>    try=!), this would at least let us experiment with new strategies
>    and PNP resource tracking etc
>  - apply Ram's patch and revert it all later if things are still broken

I think I've missed the regression discussion, so can you forward a
description and the fix?

I have to admit that I'm inclined to try the fix if it's clean, just
in the hope to get over this finally. But I'd like to see  what the
problem/fix is...

Maybe I've seen it and just didn't react.

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