Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <d8e08b16-bf99-2d0e-e666-982aa585aa5d@oracle.com>
Date:   Mon, 12 Dec 2022 11:59:51 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.5.1
Subject: Re: [PATCH 1/1] NFSD: fix use-after-free in __nfs42_ssc_open()
Content-Language: en-US
To:     Chuck Lever III <chuck.lever@oracle.com>,
        Jeff Layton <jlayton@kernel.org>
Cc:     Greg KH <gregkh@linuxfoundation.org>,
        Olga Kornievskaia <kolga@netapp.com>,
        "hdthky0@gmail.com" <hdthky0@gmail.com>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
        "security@kernel.org" <security@kernel.org>
References: <1670786549-27041-1-git-send-email-dai.ngo@oracle.com>
 <7f68cb23445820b4a1c12b74dce0954f537ae5e2.camel@kernel.org>
 <56b0cb4f-dfe9-6892-7fef-1a2965cf1d99@oracle.com>
 <0ab8efccae708faa092a56c6935c33564814bfed.camel@kernel.org>
 <Y5czwRabTFiwah2b@kroah.com>
 <a47cc610af621e95ba359388e93d988f1ef5b17f.camel@kernel.org>
 <Y5dha1Hcgolctt0K@kroah.com>
 <7365935036c192bfc64cda41cb9ccb297e3eb86f.camel@kernel.org>
 <6D5F96AA-A8A7-4E19-A566-959F19A3CB0A@oracle.com>
 <6200943464679d51de50a05ab2ca1cc0c91d8685.camel@kernel.org>
 <a895cb89-f8f3-a2e1-1958-cf9379ecdcd5@oracle.com>
 <4CAE538E-9F0B-4B44-956E-C6498A37A83A@oracle.com>
 <aefea8e45e99ba948acf4c5744793b6ad674a66c.camel@kernel.org>
 <1EAC1016-CB25-4695-A035-5DA2AA5EF58A@oracle.com>
From:   dai.ngo@oracle.com
In-Reply-To: <1EAC1016-CB25-4695-A035-5DA2AA5EF58A@oracle.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?N29oL3dZUWorbEN4b1licVF3YTF6ZGpyR1lDYlVma3hxOTRodXlURWwzTGtQ?=
 =?utf-8?B?T0RHWHZRSFQ4eVowc2hackhFQlUyWlc0RXNCT2t2RmZCcm9nMTlSendwazBB?=
 =?utf-8?B?WFNPYjg2M0ZxMi8velFPT2tYYjJ0OWVNeUNYVTZqSnZHaCtHVmtEaXlVdnJV?=
 =?utf-8?B?RnRBL0tUSnZtUUdXQmtLOWVUZDU0blowRWVXczd0OFBpd05vU2h0MWEzRXZU?=
 =?utf-8?B?MXRLSURxYk1sY3VrSUVpVXk1UmFlSWFHenFKZ1pXb2ZLbFBueHd3bnc1Z2Jx?=
 =?utf-8?B?alBxUHp3emU1WE40eHh2ZHp3NFV2RVVDb25BbnlLYWlVaElkQmJLRjlqMVZR?=
 =?utf-8?B?U1ZvWUttUUQyZHY5MlZYOEYzZ3VBRHp4ekdLVUtaT0FSek1vUHJKeXhrR09W?=
 =?utf-8?B?VTFqT1E2KzNhS000WWlXM1YwbFN0a3FUcmJFODVmODFOTVpWK0dFa1ZPTzhC?=
 =?utf-8?B?elhiMGJ0WUgyTGhWQzV0OUtBUC9mSmhCWXZsbHk4UWVPM1g1V1BlZmY3ZUt2?=
 =?utf-8?B?MXkzeEpZbng0dDN4Q0Roc2djYXNLdldBVzFEQmd5dzVOcDhrc1FqM3NQZFM2?=
 =?utf-8?B?SDNyRlh5aTByOTNyeENWekVIdENQV0k5VEkvbkNETmZDUWJkWVRDcjNBVzli?=
 =?utf-8?B?aWwxMk5rNFE5MGVtUHA4RUlQQzl1cnFiWWVsR0pqbngrVlFiZktPR2xyanJ3?=
 =?utf-8?B?Vko3d1F1cDVva2NLYU11TGowZWRxWU5ocnU0dk1RWklxTGdOR1JQL3pVRWZ4?=
 =?utf-8?B?cnEzWXJlTk9BSG0zWnRhNURPSUhzUmxuYlA0dDBibWQ4Zmp4UXJTMktQcXI2?=
 =?utf-8?B?RHc5OWlHMnVCVEN1RHhDS1Y4ZXZSa1NuVUNXTkNHcTdJdUZiNWY3RnUwT0Rq?=
 =?utf-8?B?YmpUbG51WWs5WDVjL0xMbk5laGNDMUF0VkhWV09FUElIdGJFWlVYSlo5cUkr?=
 =?utf-8?B?NzFwN2JqWDQ3NVl3R1ZaRExzMFNiV3FzK21HTTB1cXlWeENLdjAzNUhYdWJx?=
 =?utf-8?B?eWF2alFUR3VYYVBiMS82Z0ZqTFdNdmJ2OWlpTC9OOC9ZTDN5NUw5ZVdoZlh0?=
 =?utf-8?B?Q1Q1VG54a2doR2wyd1M1YytTZ2tQQ1lxOHg4QUFhU0hhN0J5ZWVpVXlPU2ti?=
 =?utf-8?B?ckFoRE1sQUQ3d09pdHU2c1ZiRktVM3FNM21PdXBxejMxaW1oeGtSd0pZSkg3?=
 =?utf-8?B?SStPMzRvR2VVVE9TdG94Q1lpYnk2bHE3cEYxVS9panhNZVBlS2dhVDlHVHpV?=
 =?utf-8?B?YWhUZGM2U21ReHpMNW9DdTBwcnlJY1hFV0tlOS9Bb3ptSEtiblpDVUxMS0pv?=
 =?utf-8?B?N2tuSWNidkJuV21NOUMrSVlTYTdvZC9rTDhHS285TVAycEE5bVk3T0ZrRjE3?=
 =?utf-8?B?ZWE4bUNvR043NnRDSytmanhDemFFN1QwaThxVWJOd2RZcTdrTzdlQlhiVHlX?=
 =?utf-8?B?dWNLV0R3V1hybWhUejJPUW55ZE1BRXNTUXQ5dldPNWhVb3V5bUNqK25seC9D?=
 =?utf-8?B?dFFWYmwwUlg5Q0RqYm5DN2s5U1h6Lzg1eHJSSjNVa0dLZUZwWThhSlpiVTEx?=
 =?utf-8?B?NG1QTXJFZXNhK1VwL29ydEhRbUczQWNSbE4xSTRqcXNEamplU3VyU1BWOVhI?=
 =?utf-8?B?aVFsWFNXMklHZ25JZ0JKdVBXV1liVDJ6MXVJejIxOVVlR3JxNnpjRWUzbDRZ?=
 =?utf-8?B?MDFUUHZvelE4ZVk1dHh1VnVLR0g2ZEJ1eW9XMW9TcjNRMlNibHY3ck1rWlJ5?=
 =?utf-8?B?ay80eUNBSGtxQk9CQ0RXVXNPb0IxSEtNZ056TFUxd3NnZWowSFBOYnJQU21y?=
 =?utf-8?B?bDJraUM2M2Z1N2lKYnoxVG5PUmx6d2FtRVloaTNRQzlQWktyZ0o4ZkFCdzhB?=
 =?utf-8?B?YkRGRnlMQ1hrVGpvS3Bpb1R6NEMwdTRWRTdMYXlMU2xveDNmR0JhNyswMmls?=
 =?utf-8?B?QlB1bFlxTHBGZG9CTjl1Q3VvNWpYdW14ZzNXUGNTRFRFN2R1V2RNdEFGSExr?=
 =?utf-8?B?SC9FZGhWbjZSQm1lbTJYd3JVWjgxRDNBUVRTejgraHpYSEFySlVLNnJYZjho?=
 =?utf-8?B?Q2M3NmhDTEJaTzlXLzcxZFBtSmErSmRXZkZaRFhJb3NrVkZIakNjOWFRSUp2?=
 =?utf-8?Q?my6aw7ER55te060h/uiFhedev?=
X-OriginatorOrg: oracle.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9009eba3-70bb-4376-2d6d-08dadc7b7007
X-MS-Exchange-CrossTenant-AuthSource: BY5PR10MB4257.namprd10.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Dec 2022 19:59:54.6046
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 4e2c6054-71cb-48f1-bd6c-3a9705aca71b
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 3WWFl72MHr/1yrxTZUmjQN6adAY6558aeBjKvN2Nf9m2Qq2vs0TZCXtKRWXAzrN+icZNazStBG2VbJIl4YUlig==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH7PR10MB6460
X-Proofpoint-Virus-Version: vendor=baseguard
 engine=ICAP:2.0.205,Aquarius:18.0.923,Hydra:6.0.545,FMLib:17.11.122.1
 definitions=2022-12-12_02,2022-12-12_02,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxlogscore=999 mlxscore=0
 adultscore=0 malwarescore=0 spamscore=0 phishscore=0 suspectscore=0
 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2210170000
 definitions=main-2212120179
X-Proofpoint-GUID: gGGze-9jiDY2JGadz6t430acLUyO-cVO
X-Proofpoint-ORIG-GUID: gGGze-9jiDY2JGadz6t430acLUyO-cVO
X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,
        DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,
        RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=ham
        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: <linux-nfs.vger.kernel.org>
X-Mailing-List: linux-nfs@vger.kernel.org


On 12/12/22 11:48 AM, Chuck Lever III wrote:
>
>> On Dec 12, 2022, at 2:46 PM, Jeff Layton <jlayton@kernel.org> wrote:
>>
>> On Mon, 2022-12-12 at 19:28 +0000, Chuck Lever III wrote:
>>>> On Dec 12, 2022, at 2:16 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>>>>
>>>>
>>>> On 12/12/22 10:38 AM, Jeff Layton wrote:
>>>>> On Mon, 2022-12-12 at 18:16 +0000, Chuck Lever III wrote:
>>>>>>> On Dec 12, 2022, at 12:44 PM, Jeff Layton <jlayton@kernel.org> wrote:
>>>>>>>
>>>>>>> On Mon, 2022-12-12 at 18:14 +0100, Greg KH wrote:
>>>>>>>> On Mon, Dec 12, 2022 at 09:31:19AM -0500, Jeff Layton wrote:
>>>>>>>>> On Mon, 2022-12-12 at 14:59 +0100, Greg KH wrote:
>>>>>>>>>> On Mon, Dec 12, 2022 at 08:40:31AM -0500, Jeff Layton wrote:
>>>>>>>>>>> On Mon, 2022-12-12 at 05:34 -0800, dai.ngo@oracle.com wrote:
>>>>>>>>>>>> On 12/12/22 4:22 AM, Jeff Layton wrote:
>>>>>>>>>>>>> On Sun, 2022-12-11 at 11:22 -0800, Dai Ngo wrote:
>>>>>>>>>>>>>> Problem caused by source's vfsmount being unmounted but remains
>>>>>>>>>>>>>> on the delayed unmount list. This happens when nfs42_ssc_open()
>>>>>>>>>>>>>> return errors.
>>>>>>>>>>>>>> Fixed by removing nfsd4_interssc_connect(), leave the vfsmount
>>>>>>>>>>>>>> for the laundromat to unmount when idle time expires.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Reported-by: Xingyuan Mo <hdthky0@gmail.com>
>>>>>>>>>>>>>> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>> fs/nfsd/nfs4proc.c | 23 +++++++----------------
>>>>>>>>>>>>>> 1 file changed, 7 insertions(+), 16 deletions(-)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
>>>>>>>>>>>>>> index 8beb2bc4c328..756e42cf0d01 100644
>>>>>>>>>>>>>> --- a/fs/nfsd/nfs4proc.c
>>>>>>>>>>>>>> +++ b/fs/nfsd/nfs4proc.c
>>>>>>>>>>>>>> @@ -1463,13 +1463,6 @@ nfsd4_interssc_connect(struct nl4_server *nss, struct svc_rqst *rqstp,
>>>>>>>>>>>>>> 	return status;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -static void
>>>>>>>>>>>>>> -nfsd4_interssc_disconnect(struct vfsmount *ss_mnt)
>>>>>>>>>>>>>> -{
>>>>>>>>>>>>>> -	nfs_do_sb_deactive(ss_mnt->mnt_sb);
>>>>>>>>>>>>>> -	mntput(ss_mnt);
>>>>>>>>>>>>>> -}
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> /*
>>>>>>>>>>>>>>   * Verify COPY destination stateid.
>>>>>>>>>>>>>>   *
>>>>>>>>>>>>>> @@ -1572,11 +1565,6 @@ nfsd4_cleanup_inter_ssc(struct vfsmount *ss_mnt, struct file *filp,
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -static void
>>>>>>>>>>>>>> -nfsd4_interssc_disconnect(struct vfsmount *ss_mnt)
>>>>>>>>>>>>>> -{
>>>>>>>>>>>>>> -}
>>>>>>>>>>>>>> -
>>>>>>>>>>>>>> static struct file *nfs42_ssc_open(struct vfsmount *ss_mnt,
>>>>>>>>>>>>>> 				   struct nfs_fh *src_fh,
>>>>>>>>>>>>>> 				   nfs4_stateid *stateid)
>>>>>>>>>>>>>> @@ -1762,7 +1750,8 @@ static int nfsd4_do_async_copy(void *data)
>>>>>>>>>>>>>> 		struct file *filp;
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 		filp = nfs42_ssc_open(copy->ss_mnt, &copy->c_fh,
>>>>>>>>>>>>>> -				      &copy->stateid);
>>>>>>>>>>>>>> +					&copy->stateid);
>>>>>>>>>>>>>> +
>>>>>>>>>>>>>> 		if (IS_ERR(filp)) {
>>>>>>>>>>>>>> 			switch (PTR_ERR(filp)) {
>>>>>>>>>>>>>> 			case -EBADF:
>>>>>>>>>>>>>> @@ -1771,7 +1760,7 @@ static int nfsd4_do_async_copy(void *data)
>>>>>>>>>>>>>> 			default:
>>>>>>>>>>>>>> 				nfserr = nfserr_offload_denied;
>>>>>>>>>>>>>> 			}
>>>>>>>>>>>>>> -			nfsd4_interssc_disconnect(copy->ss_mnt);
>>>>>>>>>>>>>> +			/* ss_mnt will be unmounted by the laundromat */
>>>>>>>>>>>>>> 			goto do_callback;
>>>>>>>>>>>>>> 		}
>>>>>>>>>>>>>> 		nfserr = nfsd4_do_copy(copy, filp, copy->nf_dst->nf_file,
>>>>>>>>>>>>>> @@ -1852,8 +1841,10 @@ nfsd4_copy(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>>>>>>>>>>>>>> 	if (async_copy)
>>>>>>>>>>>>>> 		cleanup_async_copy(async_copy);
>>>>>>>>>>>>>> 	status = nfserrno(-ENOMEM);
>>>>>>>>>>>>>> -	if (nfsd4_ssc_is_inter(copy))
>>>>>>>>>>>>>> -		nfsd4_interssc_disconnect(copy->ss_mnt);
>>>>>>>>>>>>>> +	/*
>>>>>>>>>>>>>> +	 * source's vfsmount of inter-copy will be unmounted
>>>>>>>>>>>>>> +	 * by the laundromat
>>>>>>>>>>>>>> +	 */
>>>>>>>>>>>>>> 	goto out;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>> This looks reasonable at first glance, but I have some concerns with the
>>>>>>>>>>>>> refcounting around ss_mnt elsewhere in this code. nfsd4_ssc_setup_dul
>>>>>>>>>>>>> looks for an existing connection and bumps the ni->nsui_refcnt if it
>>>>>>>>>>>>> finds one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> But then later, nfsd4_cleanup_inter_ssc has a couple of cases where it
>>>>>>>>>>>>> just does a bare mntput:
>>>>>>>>>>>>>
>>>>>>>>>>>>>         if (!nn) {
>>>>>>>>>>>>>                 mntput(ss_mnt);
>>>>>>>>>>>>>                 return;
>>>>>>>>>>>>>         }
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>         if (!found) {
>>>>>>>>>>>>>                 mntput(ss_mnt);
>>>>>>>>>>>>>                 return;
>>>>>>>>>>>>>         }
>>>>>>>>>>>>>
>>>>>>>>>>>>> The first one looks bogus. Can net_generic return NULL? If so how, and
>>>>>>>>>>>>> why is it not a problem elsewhere in the kernel?
>>>>>>>>>>>> it looks like net_generic can not fail, no where else check for NULL
>>>>>>>>>>>> so I will remove this check.
>>>>>>>>>>>>
>>>>>>>>>>>>> For the second case, if the ni is no longer on the list, where did the
>>>>>>>>>>>>> extra ss_mnt reference come from? Maybe that should be a WARN_ON or
>>>>>>>>>>>>> BUG_ON?
>>>>>>>>>>>> if ni is not found on the list then it's a bug somewhere so I will add
>>>>>>>>>>>> a BUG_ON on this.
>>>>>>>>>>>>
>>>>>>>>>>> Probably better to just WARN_ON and let any references leak in that
>>>>>>>>>>> case. A BUG_ON implies a panic in some environments, and it's best to
>>>>>>>>>>> avoid that unless there really is no choice.
>>>>>>>>>> WARN_ON also causes machines to boot that have panic_on_warn enabled.
>>>>>>>>>> Why not just handle the error and keep going?  Why panic at all?
>>>>>>>>>>
>>>>>>>>> Who the hell sets panic_on_warn (outside of testing environments)?
>>>>>>>> All cloud providers and anyone else that wants to "kill the system that
>>>>>>>> had a problem and have it reboot fast" in order to keep things working
>>>>>>>> overall.
>>>>>>>>
>>>>>>> If that's the case, then this situation would probably be one where a
>>>>>>> cloud provider would want to crash it and come back. NFS grace periods
>>>>>>> can suck though.
>>>>>>>
>>>>>>>>> I'm
>>>>>>>>> suggesting a WARN_ON because not finding an entry at this point
>>>>>>>>> represents a bug that we'd want reported.
>>>>>>>> Your call, but we are generally discouraging adding new WARN_ON() for
>>>>>>>> anything that userspace could ever trigger.  And if userspace can't
>>>>>>>> trigger it, then it's a normal type of error that you need to handle
>>>>>>>> anyway, right?
>>>>>>>>
>>>>>>>> Anyway, your call, just letting you know.
>>>>>>>>
>>>>>>> Understood.
>>>>>>>
>>>>>>>>> The caller should hold a reference to the object that holds a vfsmount
>>>>>>>>> reference. It relies on that vfsmount to do a copy. If it's gone at this
>>>>>>>>> point where we're releasing that reference, then we're looking at a
>>>>>>>>> refcounting bug of some sort.
>>>>>>>> refcounting in the nfsd code, or outside of that?
>>>>>>>>
>>>>>>> It'd be in the nfsd code, but might affect the vfsmount refcount. Inter-
>>>>>>> server copy is quite the tenuous house of cards. ;)
>>>>>>>
>>>>>>>>> I would expect anyone who sets panic_on_warn to _desire_ a panic in this
>>>>>>>>> situation. After all, they asked for it. Presumably they want it to do
>>>>>>>>> some coredump analysis or something?
>>>>>>>>>
>>>>>>>>> It is debatable whether the stack trace at this point would be helpful
>>>>>>>>> though, so you might consider a pr_warn or something less log-spammy.
>>>>>>>> If you can recover from it, then yeah, pr_warn() is usually best.
>>>>>>>>
>>>>>>> It does look like Dai went with pr_warn on his v2 patch.
>>>>>>>
>>>>>>> We'd "recover" by leaking a vfsmount reference. The immediate crash
>>>>>>> would be avoided, but it might make for interesting "fun" later when you
>>>>>>> went to try and unmount the thing.
>>>>>> This is a red flag for me. If the leak prevents the system from
>>>>>> shutting down reliably, then we need to do something more than
>>>>>> a pr_warn(), I would think.
>>>>>>
>>>>> Sorry, I should correct myself.
>>>>>
>>>>> We wouldn't (necessarily) leak a vfsmount reference. If the entry was no
>>>>> longer on the list, then presumably it has already been cleaned up and
>>>>> the vfsmount reference put.
>>>> I think the issue here is not vfsmount reference count. The issue is that
>>>> we could not find a nfsd4_ssc_umount_item on the list that matches the
>>>> vfsmount ss_mnt. So the question is what should we do in this case?
>>>>
>>>> Prior to this patch, when we hit this scenario we just go ahead and
>>>> unmount the ss_mnt there since it won't be unmounted by the laundromat
>>>> (it's not on the delayed unmount list).
>>>>
>>>> With this patch, we don't even unmount the ss_mnt, we just do a pr_warn.
>>>>
>>>> I'd prefer to go back to the previous code to do the unmount and also
>>>> do a pr_warn.
>>>>
>>>>> It's still a bug though since we _should_ still have a reference to the
>>>>> nfsd4_ssc_umount_item at this point. So this is really just a potential
>>>>> use-after-free.
>>>> The ss_mnt still might have a reference on the nfsd4_ssc_umount_item
>>>> but we just can't find it on the list. Even though the possibility for
>>>> this to happen is from slim to none, we still have to check for it.
>>>>
>>>>> FWIW, the object handling here is somewhat weird as the copy operation
>>>>> holds a reference to the nfsd4_ssc_umount_item but passes around a
>>>>> pointer to the vfsmount
>>>>>
>>>>> I have to wonder if it'd be cleaner to have nfsd4_setup_inter_ssc pass
>>>>> back a pointer to the nfsd4_ssc_umount_item, so you could pass that to
>>>>> nfsd4_cleanup_inter_ssc and skip searching for it again at cleanup time.
>>>> Yes, I think returning a pointer to the nfsd4_ssc_umount_item approach
>>>> would be better.  We won't have to deal with the situation where we can't
>>>> find an item on the list (even though it almost never happen).
>>>>
>>>> Can we do this enhancement after fixing this use-after-free problem, in
>>>> a separate patch series?
>> ^^^
>> I think that'd be best.
>>
>>> Is there a reason not fix it correctly now?
>>>
>>> I'd rather not merge a fix that leaves the possibility of a leak.
>> We're going to need to backport this to earlier kernels and it'll need
>> to go in soon. I think it'd be to take a minimal fix for the reported
>> crash, and then Dai can have some time to do a larger cleanup.
> Backporting is important, of course.
>
> What I was hearing was that the simple fix couldn't be done without
> introducing a leak or UAF.

No, this is not true. This fix is independent of the enhancement
suggested by Jeff to deal with the way the vfsmount is passed around
to avoid the condition where the ni item is not found on the list.

-Dai

>
>
> --
> Chuck Lever
>
>
>