On Mon, May 30, 2016 at 11:54 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On 5/30/16, Andreas Gruenbacher <agruenba@xxxxxxxxxx> wrote: >> This is version 3 of the xattr inode operation removal patch series. The >> patches are available in git form at: >> >> >> https://git.kernel.org/cgit/linux/kernel/git/agruen/linux.git/log/?h=work.xattr [...] >> > Hi, > > I pulled in agruen/linux.git#work.xattr on top of Linux v4.7-rc1 and noticed... > > 92 files changed, 563 insertions(+), 703 deletions(-) > > So this is on top of Linux v4.7-rc1+? Well, I've actually rebased the patches on top of commit b02b1fbd which is the current mainline and one merge after v4.7-rc1, but the few scsi commits in between -rc1 and b02b1fbd are completely unrelated. You can easily see that in git. > I am here on Ubuntu/precise AMD64 realized as a WUBI-installation. > So I use fuse, loop-device and ext4-fs. > > Not sure, how to test your patchset. > Can you give some instructions on a testcase/usecase? The patches potentially affect xattrs and anthing that's xattr based, like POSIX ACLs, SELinux, and Smack. There are some POSX ACL tests in xfstests. The basic xattr functionality can of course be checked with getfattr / setfattr. Other than that, I can probably only refer you to the code itself. > Booting into a kernel with your patchset looks fine to me - on the 1st sight. Okay, thanks. Andreas -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
