linux-kernel - Re: [PATCH] misc/pvpanic-pci: Allow automatic loading

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: <5e3f7609-4820-6a8b-306e-553f10ce0f8a@redhat.com>
Date:   Mon, 28 Jun 2021 17:44:13 +0200
From:   Eric Auger <eric.auger@...hat.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     eric.auger.pro@...il.com, linux-kernel@...r.kernel.org,
        mihai.carabas@...cle.com, arnd@...db.de, pizhenwei@...edance.com,
        andriy.shevchenko@...ux.intel.com, pbonzini@...hat.com,
        joe@...ches.com
Subject: Re: [PATCH] misc/pvpanic-pci: Allow automatic loading

Hi Greg,

On 6/28/21 4:54 PM, Greg KH wrote:
> On Mon, Jun 28, 2021 at 04:44:22PM +0200, Eric Auger wrote:
>> The pvpanic-pci driver does not auto-load and requires manual
>> modprobe. Let's include a device database using the
>> MODULE_DEVICE_TABLE macro.
>>
>> Signed-off-by: Eric Auger <eric.auger@...hat.com>
>> ---
>>  drivers/misc/pvpanic/pvpanic-pci.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/misc/pvpanic/pvpanic-pci.c b/drivers/misc/pvpanic/pvpanic-pci.c
>> index 9ecc4e8559d5d..30290d42d8aa8 100644
>> --- a/drivers/misc/pvpanic/pvpanic-pci.c
>> +++ b/drivers/misc/pvpanic/pvpanic-pci.c
>> @@ -122,4 +122,6 @@ static struct pci_driver pvpanic_pci_driver = {
>>  	},
>>  };
>>  
>> +MODULE_DEVICE_TABLE(pci, pvpanic_pci_id_tbl);
>> +
> Is this something that you need?  Or is it created by a tool?

the virtual machine monitor (QEMU) exposes the pvpanic-pci device to the
guest. On guest side the module exists but currently isn't loaded
automatically. So the driver fails to be probed and does not its job of
handling guest panic events. We need a SW actor that loads the module
and I thought this should be handled that way. If not, please could you
advise?

Thank you in advance

Eric 
>
> thanks,
>
> greg k-h
>