From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752059AbbCGQKH (ORCPT ); Sat, 7 Mar 2015 11:10:07 -0500 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.231]:63258 "EHLO cdptpa-oedge-vip.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751778AbbCGQKD (ORCPT ); Sat, 7 Mar 2015 11:10:03 -0500 From: Jeff Layton To: linux-fsdevel@vger.kernel.org Cc: bfields@fieldses.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/4] locks: locks related cleanups for v4.1 Date: Sat, 7 Mar 2015 11:09:55 -0500 Message-Id: <1425744599-4934-1-git-send-email-jeff.layton@primarydata.com> X-Mailer: git-send-email 2.1.0 X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Nothing terribly earth-shattering here. Just a few locking-related cleanup patches that I'm planning to queue up for v4.1. The only one that really warrants close attention is the 4th one that gets rid of the i_lock protection around the i_flctx pointer. One of the earlier patchsets that added the i_flctx field used cmpxchg to assign it, but I ended up taking that out due to a problem that Sasha Levin reported. I now think that I misunderstood the problem and that using cmpxchg for that should be ok. Jeff Layton (4): locks: don't allocate a lock context for an F_UNLCK request locks: change lm_get_owner and lm_put_owner prototypes locks: get rid of WE_CAN_BREAK_LSLK_NOW dead code locks: use cmpxchg to assign i_flctx pointer fs/locks.c | 45 +++++++++++++++++++-------------------------- fs/nfsd/nfs4state.c | 18 ++++++++++-------- include/linux/fs.h | 4 ++-- 3 files changed, 31 insertions(+), 36 deletions(-) -- 2.1.0