Bug 216449
Summary: | vfio-pci calls pci_bus_reset whenever a pci_release is triggered and refcnt is zero | ||
---|---|---|---|
Product: | Drivers | Reporter: | a-dibacco (a.dibacco.ks) |
Component: | PCI | Assignee: | drivers_pci (drivers_pci) |
Status: | NEW --- | ||
Severity: | normal | CC: | alex.williamson |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.x | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
a-dibacco
2022-09-05 08:21:24 UTC
This is the expected behavior, the kernel cannot know if you or some other user will get the device next and whether the state of the device contains sensitive information. Imagine a GPU that might contain a frame buffer from the previous user or a crypto device still holding a keychain. Therefore we always try to reset the device when it is released by the user. I understand your point and I agree with the choice. Anyway, wouldn't be possible to add a new module parameter that disables reset on close? I mean a parameter like disable_reset_on_close with a default value that mimic the current behaviour. I'm not an expert but it could be that there are applications that don't need to reset the device when they have finished configuring it. Keeping the device open could be a risk because in case of a software crash the device would be closed potentially affecting the functionality of the hardware. Thank you for your answer. |