Messages in this thread | | | From | Peter Chubb <> | Date | Wed, 23 Apr 2003 10:43:43 +1000 | Subject | [PATCH] struct loop_info64 |
| |
>>>>> "Andries" == Andries Brouwer <Andries.Brouwer@cwi.nl> writes:
Andries> OK, upon general request, a shorter version. It has struct Andries> loop_info64 and __kernel_old_dev_t. Otherwise mostly as Andries> before.
Andries> Andries
While you're fixing this part of the interface, can you make the loop_info64 structure large-file and large-block-device safe?
+struct loop_info64 { ... + int lo_offset; loff_t lo_offset;
And for stuff transferred between user/kernel space, it's *usually* better not to use int or long, but to use explicitly-sized types, which allows, say, both 32 and 64-bit user spaces on top of a 64-bit kernel.
Peter C - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |