Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp467267ybl; Wed, 28 Aug 2019 00:12:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqyM8BIxGDsetk+nUFybXYP1aVaVaoEqT24NPOfgVto2J8LIYwQcrM+GN+wvl0+AxlflpuCg X-Received: by 2002:a62:2c94:: with SMTP id s142mr2972495pfs.45.1566976366138; Wed, 28 Aug 2019 00:12:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566976366; cv=none; d=google.com; s=arc-20160816; b=LgQaMa9n3uRbfZE07ku74gfBs70L2KndjyRU5yrjySNYgFHrV+6UND0nIkVogkUyuJ 9hf1mfiMdjQhHUXnlxY+phAfw8VmBrHWm+dzRbQq2+nHJi75Ha2M8IXXDxhEPFeHMyv3 TDks6oWUcCfX+cOXllCht54H0e+ehqfBStdBehqaKiLBQ5fHuUFaCbGYUtQ908CBpVZp EaokkPv6wRw/WOwLgax1xZR7QaMK65Hi6clZieGdPlikgKGZ82wIdTzv0INDcxSaadOO bKcWXy2+MrNvLRQRh9CQU7dvRsapLmcmGDzfi1cGqqkLyBVaOZYnZxOrDuTzsliOriYA DmSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ibKNI+mELBabtTeEjVE4/v4qETslQUi7mw1JAIYcKqU=; b=rW5std6lisEIyWDYW6BqnWQYF/KgXY4gsP5XtxsMFtHa0hLttTzkK290DVVx9KNAPI /FgovzWEZkGqVAwlRd2YLJy6b6J7ybwAT9utGz18sUjlQAIITsxHTz9Q73PYnqFLDSzt o2+1zLxT7RdylK7Sq0GcFMNzm6uJWcg5bkE+yjIaPn9UppoqMZ5FuzAQWK4QuVfXSjmb SqtCwnC49iYTBtcTlqvRvDsnLkxeAmLdkA53EniUVBh+4jnloxibZE8u/fY+5pF4v4KF LEnPGVBYzKeAOTQzWAfFIBPVOSP7Xl6jlh6e5wEGbAPeDgXt9SZTsYaDsZCttyg97/VC 3jsw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id gn17si1227614plb.170.2019.08.28.00.12.29; Wed, 28 Aug 2019 00:12:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726497AbfH1HLX (ORCPT + 99 others); Wed, 28 Aug 2019 03:11:23 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:54935 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726399AbfH1HLX (ORCPT ); Wed, 28 Aug 2019 03:11:23 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id E66BF81849; Wed, 28 Aug 2019 09:11:06 +0200 (CEST) Date: Wed, 28 Aug 2019 09:11:19 +0200 From: Pavel Machek To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Trond Myklebust , Steve Dickson , David Howells , Sasha Levin Subject: Re: [PATCH 4.19 35/98] NFS: Fix regression whereby fscache errors are appearing on nofsc mounts Message-ID: <20190828071119.GA10462@amd> References: <20190827072718.142728620@linuxfoundation.org> <20190827072720.043818271@linuxfoundation.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <20190827072720.043818271@linuxfoundation.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue 2019-08-27 09:50:14, Greg Kroah-Hartman wrote: > [ Upstream commit dea1bb35c5f35e0577cfc61f79261d80b8715221 ] >=20 > People are reporing seeing fscache errors being reported concerning > duplicate cookies even in cases where they are not setting up fscache > at all. The rule needs to be that if fscache is not enabled, then it > should have no side effects at all. >=20 > To ensure this is the case, we disable fscache completely on all superblo= cks > for which the 'fsc' mount option was not set. In order to avoid issues > with '-oremount', we also disable the ability to turn fscache on via > remount. Actually, the code seems to suggest that you disable the ability to turn fscache _off_ via remount, too. Is that intentional? Best regards, Pavel > @@ -2239,6 +2239,7 @@ nfs_compare_remount_data(struct nfs_server *nfss, > data->acdirmin !=3D nfss->acdirmin / HZ || > data->acdirmax !=3D nfss->acdirmax / HZ || > data->timeo !=3D (10U * nfss->client->cl_timeout->to_initval / HZ) = || > + (data->options & NFS_OPTION_FSCACHE) !=3D (nfss->options & NFS_OPTI= ON_FSCACHE) || > data->nfs_server.port !=3D nfss->port || > data->nfs_server.addrlen !=3D nfss->nfs_client->cl_addrlen || > !rpc_cmp_addr((struct sockaddr *)&data->nfs_server.address, --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl1mKRcACgkQMOfwapXb+vIEvACfVpzLbeyLcBleN3N5tPiXdRHY yqsAoKVSoLdRl2MIVRw24zZV2bl8V+9T =hqyc -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--