On 10/05/2014 4:15 AM, Jeff Layton wrote:
Well spotted -- that was indeed unintentional. Fixed in my repo and in the code in -next, but I'll refrain from re-posting for now. Clearly, I need to roll some better file locking tests... ;) Thanks,
I've just applied the following 3 patches from Jeff's git repo on top of a vanilla 3.15-rc5:
09e558d9baa6416111bce8610c6bbd9a525ee057 [PATCH] locks: only validate the lock vs. f_mode in F_SETLK codepaths
e4bf5e2a931bdf053e5bcb72ec959ee151ef2aaf [PATCH] locks: ensure that fl_owner is always initialized properly in flock and lease codepaths
0e71bcb3ec5d8fba7e534d379ad69933ed6493e0 [PATCH] fs/locks.c: replace seq_printf by seq_puts
I can confirm that this fixes the problem - in that Samba now compiles through to completion.
Thanks for the fix! Reuben -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
