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: <CAHp75Vd8mEZRTVYiR5Nz4X8HM8VUHArc5C1SyfN4K8c-Y9+taw@mail.gmail.com>
Date:   Mon, 26 Feb 2018 16:34:26 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Corey Minyard <minyard@....org>
Cc:     Chris Chiu <chiu@...lessm.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Upstreaming Team <linux@...lessm.com>,
        openipmi-developer@...ts.sourceforge.net,
        Corey Minyard <cminyard@...sta.com>
Subject: Re: [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device

On Mon, Feb 26, 2018 at 4:50 AM,  <minyard@....org> wrote:

> Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
> KCS controller, but whatever it is, it's not one.  Ignore it if seen.

> +static struct pci_device_id ipmi_pci_blacklist[] = {
> +       /*
> +        * This is a "Virtual IPMI device", whatever that is.  It appears
> +        * as a KCS device by the class, but it is not one.
> +        */

> +       { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x816c) },
> +       { 0, }

{ PCI_VDEVICE(REALTEK, 0x816c) },
{ }

?

> +};

> +       if (pci_match_id(ipmi_pci_blacklist, pdev))
> +               return -ENODEV;


-- 
With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ