On Tue, 2017-05-30 at 12:31 -0400, Benjamin Coddington wrote: > LTP fcntl tests (fcntl11 fcntl14 fcntl17 fcntl19 fcntl20 fcntl21) have been > failing for NFSv4 mounts due to an unexpected l_pid. What follows are some > fixups: > > on v2: > - Rebase onto linux-next > - Revert back to using the stack in locks_mandatory_area(), and fixup > patch description for 1/3 > - Add a comment to 3/3 explaining the seemingly-redundant fl_pid and > fl_nspid > > These three patches can be pulled from the branch named "fixups_for_l_pid" > here: git://bcodding.com/~bcodding/linux > > Benjamin Coddington (3): > fs/locks: Use allocation rather than the stack in fcntl_getlk() > fs/locks: Set fl_nspid at file_lock allocation > fs/locks: Use fs-specific l_pid for remote locks > > fs/locks.c | 100 ++++++++++++++++++++++++++++++++++------------------- > include/linux/fs.h | 7 ++++ > 2 files changed, 72 insertions(+), 35 deletions(-) > This all looks good to me. Nice work! I've gone ahead and merged it into my linux-next branch, and it should make v4.13 (barring any problems). Thanks! -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
