On Thu, Apr 23, 2015 at 10:43:29PM +0530, Chandan Rajendra wrote: > On Monday 20 Apr 2015 13:33:16 xuw2...@gmail.com wrote: > > From: George Wang <xuw2...@gmail.com> > > > > PPC64 arch use such following IOC values " > > \#define _IOC_NONE 1U > > \#define _IOC_READ 2U > > \#define _IOC_WRITE 4U > > " comparing to the default IOC values " > > \#define _IOC_NONE 0U > > \#define _IOC_READ 2U > > \#define _IOC_WRITE 1U" > > > > This means the value "_IOW*" will be negative when we store it in the int > > variables. Such as the "BTRFS_IOC_QGROUP_CREATE", it will be "0x4010942e" on > > X86_64, but "0x8010942e" on PPC64. > > Notice that the IOC values are the "unsigned long" type, so we use the > > "unsigned long" to store it, and this can insure the comparison between the > > variable and BTRFS_IOC_* valid. > > > > Signed-off-by: George Wang <xuw2...@gmail.com> > > Tested-by: Chandan Rajendra <chan...@linux.vnet.ibm.com>
Thanks for testing, commit updated. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
