On Mon, Jan 24, 2011 at 02:01:04PM +0100, Felix Blanke wrote: > Hi, > > you were talking about the LOOP_GET_STATUS function. I'm not quite sure where does it > came from. Is it part of the kernel? Or does it come from the util-linux package? It's an ioctl (number 0x4c03) that works on loop devices, and returns information about the loop device. Being an ioctl, it's implemented in the kernel. Unfortunately, since it's part of the kernel API, the size of the name field is probably fixed for the rest of time, and so the bug can't be fixed. > I'm searching for the right location where do report that bug :) linux-kernel mailing list, I think. > Btw: I tested it with util-linux-2.19-rc1. The strace still contains > the truncated path, and no '*'. Therefore I think that ioctl is from > the kernel. Indeed. What I find interesting is that my copy of losetup follows symlinks from the /dev/disk/by-id/... path back to the original device node (/dev/dm-7 in my test case) before setting up the loop, whereas yours seems not to. I think that that's probably the easiest solution to this problem: modify losetup to use realpath(3) on the device node it's given. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- make bzImage, not war ---
Attachment:
signature.asc
Description: Digital signature
