Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2275346rwb; Thu, 15 Dec 2022 23:05:43 -0800 (PST) X-Google-Smtp-Source: AA0mqf6+QV0cVds58hOFooHo9P2rus3ob2Acz01UKVFQ81NZDnVuClyJqVU9Q88q2DGK6D3FlDLm X-Received: by 2002:a17:902:f1c5:b0:190:c219:ae22 with SMTP id e5-20020a170902f1c500b00190c219ae22mr12898209plc.53.1671174343613; Thu, 15 Dec 2022 23:05:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671174343; cv=none; d=google.com; s=arc-20160816; b=fBlEAeZzOsifzPWDWnMzBhFBTgCr+o32QuWq41snVzL35b6cmd9yJmGiFnMsLKupcp bpiAwclOQhnGRuRPeZURlG7qvB/41aFmpZDkDbCH+BBD5MpOqQu5yhMX0TUrDwWwAsEl 05k6mW2Ilz2+c6RXSY0+c4NyRuisxwOfxQ8QAtEQdd/bIm0Tjfu6ljVVTV0B4MxuNVR4 NkzUj2Bqm8sPt/RFg0ghI1WT0wV0nTGLXOct6DJtUQ2KVSH09rtdaNMTNeWV4OP0dfXI DhjjYkZfuywwiIKD8caXkhS/g8K2uMRksZBFxxyCcSKVLihWSNc90bY70NbbycWALFHb 4djg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=EyyTXVbRxW6RoYTlLvUhbIorlI9fdIsygWbvarVeWmI=; b=kS87MMGCk87OzKesN0jLElM9TVfZbLGWQZ0RSmDis6TVwsXruznHDaMzTHdE1sg3/3 IyW5lLV75aahguHbDQlNlLSC8Wc8DDxYrP/8Xo64DZZba+uXDXCYfGtS4s8ushZa4Hj3 W2ItrFbZ/WYeV9pp0Mqd4Xm1e/PQ/uwQBcWb7PJIoWeab5ff+U+EzTd5Suz81wum3feP JW7XfvQSTaTCtqMuUcGIHdHMkqH//vbn4dqGPPjcUhR5g/JuKIET2s2vlW1pwdwc5E0C awquFNzmAk6kuXx4y4Av/6XBZBV2YLO3pNKiFJwqkBhY2TJK2v5R7n/PiqDAqfG1bHnP pFuA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UJ+wWNTd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q1-20020a170902eb8100b00186e3781ae2si1652827plg.316.2022.12.15.23.05.34; Thu, 15 Dec 2022 23:05:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UJ+wWNTd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229731AbiLPGqd (ORCPT + 69 others); Fri, 16 Dec 2022 01:46:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56260 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229708AbiLPGqa (ORCPT ); Fri, 16 Dec 2022 01:46:30 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3B33810B53 for ; Thu, 15 Dec 2022 22:45:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671173141; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EyyTXVbRxW6RoYTlLvUhbIorlI9fdIsygWbvarVeWmI=; b=UJ+wWNTd2u2LXx4Qtcm2JSkk7dpuLaCYgLYDnnxh3yw4Be4qPZqeREhBzuGDRYogu1QrXg /ZgQlvZPU6eGGWbTb35TqOmS8GxPN1YyTW0KJes9QWmvUiMCrq0Y7HM2FbNcobZwWp25X9 uvUzpHihxP9WAlBGevPdfenbUNmTYJw= Received: from mail-pf1-f199.google.com (mail-pf1-f199.google.com [209.85.210.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-52-NC3QVrd2MhqkM4L7TST4Fw-1; Fri, 16 Dec 2022 01:45:39 -0500 X-MC-Unique: NC3QVrd2MhqkM4L7TST4Fw-1 Received: by mail-pf1-f199.google.com with SMTP id 67-20020a621946000000b00575f8210320so1049834pfz.10 for ; Thu, 15 Dec 2022 22:45:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:content-transfer-encoding:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EyyTXVbRxW6RoYTlLvUhbIorlI9fdIsygWbvarVeWmI=; b=6aYWdfGgR9inwuHKA/Bct8Ss7EN7FGIjjQx6FW4NUx6EEwwIVbLdK/Va33od1+Fhw/ Jn7M4Hw+i1vLrufW9St5qsYFitenbw6xR/wc+4HlvWosA/tvla/fOYtOAYK73L32wW/5 M4tS3J26R937jt3bLp+xtzFrLUuGqfdJk1AfH5dLfklPTUnN7ZfD4Mz7SR7OddE4vmLC d1QUIz2tkr5dg+MWMPXCuMOke07chMh6i1of+g7Wu8e4b7rVAdv1dips1vZFbiymJtDG YVdR2KCEXromTMKzNX5ndZvChvM4dcNE2Z/AeYSulYyNMeLPdwO816oDJVgSP2C5+lBB cBZg== X-Gm-Message-State: ANoB5pkqKUiAOK4Cqe7F/V/GAmz05GFw+ebhhqwtdOrwmCeSaROdtsBh Ee1TITkKnlecWX4uTsV7bboD6eGq4ghNQsmVJzltbmkeTmbj6rDX/CDMJjjNkp8oQ0IieZorj9J +pd6iBZNKdU1lFmtgjt/YTCFR X-Received: by 2002:a05:6a00:324b:b0:574:3cde:385a with SMTP id bn11-20020a056a00324b00b005743cde385amr28147994pfb.32.1671173138542; Thu, 15 Dec 2022 22:45:38 -0800 (PST) X-Received: by 2002:a05:6a00:324b:b0:574:3cde:385a with SMTP id bn11-20020a056a00324b00b005743cde385amr28147984pfb.32.1671173138212; Thu, 15 Dec 2022 22:45:38 -0800 (PST) Received: from [10.72.12.85] ([209.132.188.80]) by smtp.gmail.com with ESMTPSA id b27-20020aa78edb000000b005772bf1b61bsm698482pfr.67.2022.12.15.22.45.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Dec 2022 22:45:37 -0800 (PST) Subject: Re: [PATCH v5 1/2] ceph: switch to vfs_inode_has_locks() to fix file lock bug To: Ilya Dryomov Cc: jlayton@kernel.org, ceph-devel@vger.kernel.org, mchangir@redhat.com, lhenriques@suse.de, viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, stable@vger.kernel.org References: <20221214033512.659913-1-xiubli@redhat.com> <20221214033512.659913-2-xiubli@redhat.com> From: Xiubo Li Message-ID: Date: Fri, 16 Dec 2022 14:45:30 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15/12/2022 21:20, Ilya Dryomov wrote: > On Wed, Dec 14, 2022 at 4:35 AM wrote: >> From: Xiubo Li >> >> For the POSIX locks they are using the same owner, which is the >> thread id. And multiple POSIX locks could be merged into single one, >> so when checking whether the 'file' has locks may fail. >> >> For a file where some openers use locking and others don't is a >> really odd usage pattern though. Locks are like stoplights -- they >> only work if everyone pays attention to them. >> >> Just switch ceph_get_caps() to check whether any locks are set on >> the inode. If there are POSIX/OFD/FLOCK locks on the file at the >> time, we should set CHECK_FILELOCK, regardless of what fd was used >> to set the lock. >> >> Cc: stable@vger.kernel.org >> Cc: Jeff Layton >> Fixes: ff5d913dfc71 ("ceph: return -EIO if read/write against filp that lost file locks") >> Reviewed-by: Jeff Layton >> Signed-off-by: Xiubo Li >> --- >> fs/ceph/caps.c | 2 +- >> fs/ceph/locks.c | 4 ---- >> fs/ceph/super.h | 1 - >> 3 files changed, 1 insertion(+), 6 deletions(-) >> >> diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c >> index 065e9311b607..948136f81fc8 100644 >> --- a/fs/ceph/caps.c >> +++ b/fs/ceph/caps.c >> @@ -2964,7 +2964,7 @@ int ceph_get_caps(struct file *filp, int need, int want, loff_t endoff, int *got >> >> while (true) { >> flags &= CEPH_FILE_MODE_MASK; >> - if (atomic_read(&fi->num_locks)) >> + if (vfs_inode_has_locks(inode)) >> flags |= CHECK_FILELOCK; >> _got = 0; >> ret = try_get_cap_refs(inode, need, want, endoff, >> diff --git a/fs/ceph/locks.c b/fs/ceph/locks.c >> index 3e2843e86e27..b191426bf880 100644 >> --- a/fs/ceph/locks.c >> +++ b/fs/ceph/locks.c >> @@ -32,18 +32,14 @@ void __init ceph_flock_init(void) >> >> static void ceph_fl_copy_lock(struct file_lock *dst, struct file_lock *src) >> { >> - struct ceph_file_info *fi = dst->fl_file->private_data; >> struct inode *inode = file_inode(dst->fl_file); >> atomic_inc(&ceph_inode(inode)->i_filelock_ref); >> - atomic_inc(&fi->num_locks); >> } >> >> static void ceph_fl_release_lock(struct file_lock *fl) >> { >> - struct ceph_file_info *fi = fl->fl_file->private_data; >> struct inode *inode = file_inode(fl->fl_file); >> struct ceph_inode_info *ci = ceph_inode(inode); >> - atomic_dec(&fi->num_locks); >> if (atomic_dec_and_test(&ci->i_filelock_ref)) { >> /* clear error when all locks are released */ >> spin_lock(&ci->i_ceph_lock); >> diff --git a/fs/ceph/super.h b/fs/ceph/super.h >> index 14454f464029..e7662ff6f149 100644 >> --- a/fs/ceph/super.h >> +++ b/fs/ceph/super.h >> @@ -804,7 +804,6 @@ struct ceph_file_info { >> struct list_head rw_contexts; >> >> u32 filp_gen; >> - atomic_t num_locks; >> }; >> >> struct ceph_dir_file_info { >> -- >> 2.31.1 >> > Hi Xiubo, > > You marked this for stable but there is an obvious dependency on > vfs_inode_has_locks() that just got merged for 6.2-rc1. Are you > intending to take it into stable kernels as well? In the testing branch I just removed the stable list and will do the backport myself. Thanks - Xiubo > Thanks, > > Ilya >