xfs
[Top] [All Lists]

Re: BLKGETSIZE64, BLKBSZSET, BLKSSZGET definition in xfsprogs.

To: linux-xfs@xxxxxxxxxxx
Subject: Re: BLKGETSIZE64, BLKBSZSET, BLKSSZGET definition in xfsprogs.
From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 07 Oct 2003 06:32:26 -0700
In-reply-to: <Pine.LNX.4.53.0310071107220.1331@alienAngel.home.sk>
Organization: Back to Basics Network Management
References: <Pine.LNX.4.53.0310060739360.16790@alienAngel.home.sk> <20031006055957.GC1001@frodo> <Pine.LNX.4.53.0310071107220.1331@alienAngel.home.sk>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Jan Derfinak wrote:

There was change in 2.6.0-test5 and linux/fs.h isn't included in
xfsprogs so xfsprogs uses old definition.


bzcat patch-2.6.0-test5.bz2 | grep -e BLKBSZSET -e BLKGETSIZE64

-#define BLKBSZSET _IOW(0x12,113,sizeof(int)) -#define BLKGETSIZE64 _IOR(0x12,114,sizeof(u64)) /* return device size in bytes (u64 *arg) */ +#define BLKBSZSET _IOW(0x12,113,size_t) +#define BLKGETSIZE64 _IOR(0x12,114,size_t) /* return device size in bytes (u64 *arg) */


Actually, those definitions will produce the same ioctl number, so effectively there is no change. The kernel can't really change ioctl numbers once userspace begins using them, because that's an incompatible change, so it's fine if a userspace package copies the definition of some ioctls and then uses its own copies.



<Prev in Thread] Current Thread [Next in Thread>