On 5/26/2026 8:45 PM, Michael Kelley wrote:
From: Naman Jain <[email protected]> Sent: Tuesday, May 26, 2026 3:10
AM
On 5/26/2026 1:59 PM, Ben Hutchings wrote:
On Tue, 2026-05-26 at 12:15 +0530, Naman Jain wrote:
On 5/25/2026 5:34 PM, Ben Hutchings wrote:
The Hyper-V kernel-mode fcopy driver was removed in 6.10 and the new
fcopy daemon requires this uio driver to function. However, by
default the driver does not bind to any devices, and must be
configured through the sysfs "new_id" file.
Since the FCopy device is now only usable through this driver, add its
ID to the driver's ID table so that the daemon will work "out of the
box".
Signed-off-by: Ben Hutchings <[email protected]>
Fixes: ec314f61e4fc ("Drivers: hv: Remove fcopy driver")
---
--- a/drivers/uio/uio_hv_generic.c
+++ b/drivers/uio/uio_hv_generic.c
@@ -395,9 +395,15 @@ hv_uio_remove(struct hv_device *dev)
vmbus_free_ring(dev->channel);
}
+static const struct hv_vmbus_device_id hv_uio_id_table[] = {
+ { HV_FCOPY_GUID },
+ {}
+};
+MODULE_DEVICE_TABLE(vmbus, hv_uio_id_table);
+
static struct hv_driver hv_uio_drv = {
.name = "uio_hv_generic",
- .id_table = NULL, /* only dynamic id's */
+ .id_table = hv_uio_id_table,
.probe = hv_uio_probe,
.remove = hv_uio_remove,
};
++ recipients, assuming you mistakenly clicked reply instead of reply all.
Ben --
Regarding recipients, please include the full LKML
([email protected]) on the original patch posting, even
though it is about a narrow Hyper-V issue. I dabble in areas beyond
just Hyper-V so subscribe to the full LKML instead of the
linux-hyperv mailing list. I miss patches like this one unless I happen
to be looking through the lore.kernel.org archives for linux-hyperv.
Thx,
Michael
Sashiko also misses out on such patches if [email protected]
is not included. I could not find this in https://sashiko.dev/#/.
Regards,
Naman
