Re: [PATCH] virdevmapper: Always use device name for finding targets

2025-07-10 Thread Daniel P . Berrangé via Devel
On Thu, Jul 03, 2025 at 12:39:33AM +0530, Bhavin via Devel wrote: > From: Bhavin Gandhi > > DM_TABLE_DEPS expects a device name in dm_ioctl.name. In one of the > cases, full path of the device was getting returned causing the ioctl > call to fail with `ENXIO (No such device or address)`. > > Als

Re: [PATCH] virdevmapper: Always use device name for finding targets

2025-07-10 Thread Bhavin Gandhi via Devel
On 03/07/2025 00:39, Bhavin via Devel wrote: From: Bhavin Gandhi DM_TABLE_DEPS expects a device name in dm_ioctl.name. In one of the cases, full path of the device was getting returned causing the ioctl call to fail with `ENXIO (No such device or address)`. Also rename the function and variab

Re: [PATCH] virdevmapper: Always use device name for finding targets

2025-07-02 Thread Bhavin via Devel
This was sent from a wrong mail address by mistake, sorry for the noise. Can be ignored as a duplicate.

[PATCH] virdevmapper: Always use device name for finding targets

2025-07-02 Thread bhavin192--- via Devel
From: Bhavin Gandhi DM_TABLE_DEPS expects a device name in dm_ioctl.name. In one of the cases, full path of the device was getting returned causing the ioctl call to fail with `ENXIO (No such device or address)`. Also rename the function and variable names to better reflect that we are dealing w

[PATCH] virdevmapper: Always use device name for finding targets

2025-07-02 Thread Bhavin via Devel
From: Bhavin Gandhi DM_TABLE_DEPS expects a device name in dm_ioctl.name. In one of the cases, full path of the device was getting returned causing the ioctl call to fail with `ENXIO (No such device or address)`. Also rename the function and variable names to better reflect that we are dealing w