Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8720C433FE for ; Tue, 11 Jan 2022 15:36:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343654AbiAKPgG (ORCPT ); Tue, 11 Jan 2022 10:36:06 -0500 Received: from out30-133.freemail.mail.aliyun.com ([115.124.30.133]:58141 "EHLO out30-133.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240480AbiAKPgF (ORCPT ); Tue, 11 Jan 2022 10:36:05 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R621e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e01424;MF=guwen@linux.alibaba.com;NM=1;PH=DS;RN=6;SR=0;TI=SMTPD_---0V1afBHr_1641915362; Received: from 30.39.146.113(mailfrom:guwen@linux.alibaba.com fp:SMTPD_---0V1afBHr_1641915362) by smtp.aliyun-inc.com(127.0.0.1); Tue, 11 Jan 2022 23:36:03 +0800 Message-ID: Date: Tue, 11 Jan 2022 23:36:02 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH net 1/3] net/smc: Resolve the race between link group access and termination To: Karsten Graul , davem@davemloft.net, kuba@kernel.org Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <1641806784-93141-1-git-send-email-guwen@linux.alibaba.com> <1641806784-93141-2-git-send-email-guwen@linux.alibaba.com> <8b720956-c8fe-0fe2-b019-70518d5c60c8@linux.ibm.com> From: Wen Gu In-Reply-To: <8b720956-c8fe-0fe2-b019-70518d5c60c8@linux.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks for your review. On 2022/1/11 4:23 pm, Karsten Graul wrote: > On 10/01/2022 10:26, Wen Gu wrote: >> We encountered some crashes caused by the race between the access >> and the termination of link groups. >> > > These waiters (seaparate ones for smcd and smcr) are used to wait for all lgrs > to be deleted when a module unload or reboot was triggered, so it must only be > woken up when the lgr is actually freed. Thanks for your reminding, I will move the wake-up code to __smc_lgr_free(). And maybe the vlan put and device put of smcd are also need to be moved to __smc_lgr_free()?, because it also seems to be more suitable to put these resources when lgr is actually freed. What do you think? Thanks, Wen Gu