Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp340988rwn; Wed, 7 Sep 2022 18:00:06 -0700 (PDT) X-Google-Smtp-Source: AA6agR5aQwwNTpK3919hISiKyjCPkEV92BN32RJiBsdCtAXytdp4kBheHzwhP62YQ8XIFTwaVmkR X-Received: by 2002:a05:6402:54b:b0:44e:ac69:c617 with SMTP id i11-20020a056402054b00b0044eac69c617mr5155045edx.64.1662598806374; Wed, 07 Sep 2022 18:00:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662598806; cv=none; d=google.com; s=arc-20160816; b=by4OsDPNgPji4ShxoGZflXxYmjetT23cdpriZaLlLMnIoJq+vLvX6V1+MJcKE8bNc0 /Ifrl0ElMR4JHsHl8pJJqZvp4DIjkP/GGvZmxuRVWxVMNnEow/E3BUZ2Fo8aqWJtct8Y aizgR6niSYr7JCA8La8M/27vzW8k9WHQ7nwlpQfCRRrGClTkk0oWWULVX7WgPFrlliuU uDOCQZdgIRmMTd2/6cWDFRzQg4jomwUFWVK8hb3wwX14dCkR+r0ZEdv2S18DRD95hdNE 3RREUqKpnRPJQfn7/AuDFiBuZFnq31GGM4a5EvEGAqExY02Apw5lNeykTPbiqj3uM1j1 dgeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:user-agent:from :references:in-reply-to:mime-version:dkim-signature; bh=H72+9BX1R/U8sxER2gvuLw7JGA1tmcpEapnmbRh2XHM=; b=u4n341GfVo4MOu+JBa7fo2X35K1GeyvCK4ZVPGJU22S/d7WTev5ptv+doDU7fCEt8G HzHJRhAuse1y7LoLTVc6LdqDEqS7vVxwmAHwqE2R9CBShIbR55b++hicd0zGL/Cg18XH VARJsW3wL7hF1Xs7TbMK2U6fHuvY7pLEtHrZsE9RhDpGEjTZ+SVR0h+IvmQAy0BC7zIc Mj1x9+O4kCTKTpQVdaL8pk1ALFtg99xvGSmo66OJV95D/Xci87mGwJ2N86Wo2HWaivOl yMs7NfymId+dzwLnv/atfs+/fCyHehnXaXyRj3a5GhisxGMIEn007vUpGzBu+WvzxHH6 AWPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=Zr5p7FEc; 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=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sc29-20020a1709078a1d00b007397aa27b32si876878ejc.891.2022.09.07.17.59.39; Wed, 07 Sep 2022 18:00:06 -0700 (PDT) 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=@chromium.org header.s=google header.b=Zr5p7FEc; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229980AbiIHAxE (ORCPT + 99 others); Wed, 7 Sep 2022 20:53:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229611AbiIHAxC (ORCPT ); Wed, 7 Sep 2022 20:53:02 -0400 Received: from mail-oo1-xc2a.google.com (mail-oo1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C15E7A9C1F for ; Wed, 7 Sep 2022 17:53:00 -0700 (PDT) Received: by mail-oo1-xc2a.google.com with SMTP id u3-20020a4ab5c3000000b0044b125e5d9eso2717002ooo.12 for ; Wed, 07 Sep 2022 17:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:user-agent:from:references :in-reply-to:mime-version:from:to:cc:subject:date; bh=H72+9BX1R/U8sxER2gvuLw7JGA1tmcpEapnmbRh2XHM=; b=Zr5p7FEcvb9oVD1st7VVTxLk/zQNLuiBDm9ySpOE248hDMAlhiT3ZGYS0k06vXq06r tFux+9kgQkXoimCwmcsGfx4jYMdXFmA6MD9uoUBLETjeyXmep9X5Nu2dTeA2ZgMl5qHv dZv9NYRoqxUpzxgCcB/W1r4kOFbqSoa3I8UKo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:user-agent:from:references :in-reply-to:mime-version:x-gm-message-state:from:to:cc:subject:date; bh=H72+9BX1R/U8sxER2gvuLw7JGA1tmcpEapnmbRh2XHM=; b=FXCU8odn1x9AvTmK4brVU8kay+GQJDYYnKq/HYyCxp7fn3RA4Ifq8UH+czH0/3M7DI LhN5UQKFfPhfkC7m67qQIT1GntfTrfJ1zGQTz0WezrQJQHaJkbgqCs7Y9k+GhxuhBOwO J3HCvMUvEqJqtK7ZUhqydMf2JC1yQZ3mIFRJE3hQbVjWayfxxMl4pdDIz30rJnB8jiPc F2WyOqlovIvmYnq/1kfsrrxTPODddHwmFjPjaWpD5De9ZFfKNgfCeNX2GG0AoJeaXZKM rrh3hcpbv9SF+fnacAcMuaQ6qChgKZqy2wVH0RtKVM9i6zur3yEuzc61fZPe1WO8hs0T kvSg== X-Gm-Message-State: ACgBeo0T3S5hA4vQSnSfjP9TcqYTVQyqddLgZ/QRJuio19AT5/FpuChB 6wayj60Y+IF97VMBjwHQFEYsq+Q9DW/jz5uuiG/2yg== X-Received: by 2002:a4a:80cd:0:b0:44a:dce5:bbc3 with SMTP id a13-20020a4a80cd000000b0044adce5bbc3mr2184662oog.26.1662598380105; Wed, 07 Sep 2022 17:53:00 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 7 Sep 2022 19:52:59 -0500 MIME-Version: 1.0 In-Reply-To: <1662404120-24338-1-git-send-email-quic_deesin@quicinc.com> References: <1662404120-24338-1-git-send-email-quic_deesin@quicinc.com> From: Stephen Boyd User-Agent: alot/0.10 Date: Wed, 7 Sep 2022 19:52:59 -0500 Message-ID: Subject: Re: [PATCH V2 1/2] rpmsg: glink: Add lock to avoid race when rpmsg device is released To: Deepak Kumar Singh , bjorn.andersson@linaro.org, mathieu.poirier@linaro.org, quic_clew@quicinc.com Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org Content-Type: text/plain; charset="UTF-8" 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,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Quoting Deepak Kumar Singh (2022-09-05 11:55:19) > When remote host goes down glink char device channel is freed, > At the same time user space apps can still try to open/poll rpmsg > char device which will result in calling rpmsg_create_ept. This may > cause reference to already freed context of glink chardev channel and > result in below crash signatures - > > 1) > rpmsg_create_ept+0x40/0xa0 > rpmsg_eptdev_open+0x88/0x138 > chrdev_open+0xc4/0x1c8 > do_dentry_open+0x230/0x378 > > 2) > rpmsg_poll+0x5c/0x80 > rpmsg_eptdev_poll+0x84/0xa4 > do_sys_poll+0x22c/0x5c8 > > This patch adds proper lock and check condition to avoid such crash. Usually it's nice to have a two CPU diagram that shows the problem scenario with time flowing down and interleaving the calls with indentation, instead of some callstacks. Can you add that detail here? I guess it would look like this: CPU0 CPU1 ---- ---- do_sys_poll() chrdev_open() rpmsg_eptdev_poll() rpmsg_eptdev_open() rpmsg_create_ept() rpmsg_poll() but I don't immediately understand the problem. Probably showing the free path and wherever eptdev is set to NULL will help inform better than a parallel poll and chrdev open. > > Signed-off-by: Deepak Kumar Singh > --- Any Fixes tag?