linux-kernel - Re: [PATCH] pci: Add dummy for pci_acs_enabled() if CONFIG

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: <20170922175153.phtxn5jhe7ioz4ps@suse.de>
Date:   Fri, 22 Sep 2017 19:51:53 +0200
From:   Joerg Roedel <jroedel@...e.de>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Arnd Bergmann <arnd@...db.de>,
        Alex Williamson <alex.williamson@...hat.com>,
        linux-pci@...r.kernel.org, iommu@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pci: Add dummy for pci_acs_enabled() if CONFIG_PCI=n to
 fix iommmu build

Hey Bjorn,

On Fri, Sep 22, 2017 at 10:56:05AM -0500, Bjorn Helgaas wrote:
> Joerg, if you pick this up, would you mind capitalizing the subject
> line to match the PCI convention, e.g.,
> 
>   PCI: Add dummy pci_acs_enabled() for CONFIG_PCI=n build
> 
> If it's too late for you to pick this up this week, I can include it
> next week.  I assume this is not related to a specific change, i.e.,
> it's not a regression?  Should it be marked for stable?

I sent iommu fixes out today, this was not included. So if you are
sending fixes upstream next week anyway, please pick it up. I am not
sure if I have anything to send next week, so you are probably faster.

I think its stable material too.

Thanks,

	Joerg