Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2482005pxj; Sat, 19 Jun 2021 13:46:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5Tvv4W2dltDFNbyLqM2bvLzULl4V5umnsZeRTGqieZZfEHD6332a4NVxwmCfy3lpl/WLu X-Received: by 2002:a17:906:4308:: with SMTP id j8mr16980901ejm.315.1624135586911; Sat, 19 Jun 2021 13:46:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624135586; cv=none; d=google.com; s=arc-20160816; b=05vwk9wKcSNG+vV61vbZ86kOzxSecDVshzMRSCpwKeNisFqSvWdeWvuVBbvAVPf61k JRtaxnNQ+3bP+nBEA6Chgkec5Hr6WKhyj+RDhLtjeeqXGKUNijuPseQtf9X7Rid0nXUE lJn5TeDek1TUqHv4tJGh2vdwHE1s4ZN3J7P81sg2fKS9KcTMSMUP9esBVIhc05I+5Uft UAvWhd463n1rt2/5/Lp9k/dsb5XsxhxvUCU7eOHzcv/NPpWVfHYQBrD+iXsH7iROy4CS dO+ZSQjitlZpZUI4m1KbfqOgxwaDARVmfEM8uj7p4/4JoBwmWizBsdaAYpno2TuuYFzB SnAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=WVXdgaYxOdN+KJD0Mz9yqbh9MvSBaAsLb5od8TZyvfI=; b=fyS9mHSB8CKTIo2oymC0cAy//wAYfUgH2xdbHtZe202BSqqSM8ujaZlOhF/9hd9BQR cBBMSPA6xtMjlnjs85lawkIIINTf0bgJ2m99N+szHhhsT2C132Aw989m6CSeE9ruoyv4 IERZwuZhpPINeviyJFyU6VnKNGqAcrPikp4EFs4VjarY2mlwR8iroWjd+PF6ki0hsXnF BIqWVwsaOk23Zu8z2S8LIBCxzjmGsHKEMbRx9PkF68KnzPTz/nRtFEgaCrojWNCysynE nBU7tWowhSx1Y0l2hivN1vJ8U0M0tV0UIBakoYHltCCWK4nY+t61jv/W5Ujtj+aj7RaY r5Bg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bl4si7229190ejb.689.2021.06.19.13.46.04; Sat, 19 Jun 2021 13:46:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234725AbhFSQVf (ORCPT + 99 others); Sat, 19 Jun 2021 12:21:35 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:57506 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232640AbhFSQVe (ORCPT ); Sat, 19 Jun 2021 12:21:34 -0400 Received: from 1.general.cascardo.us.vpn ([10.172.70.58] helo=localhost.localdomain) by youngberry.canonical.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1ludgn-0006fD-1c; Sat, 19 Jun 2021 16:19:21 +0000 From: Thadeu Lima de Souza Cascardo To: linux-can@vger.kernel.org Cc: Oliver Hartkopp , Marc Kleine-Budde , "David S. Miller" , Jakub Kicinski , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Thadeu Lima de Souza Cascardo , syzbot+0f7e7e5e2f4f40fa89c0@syzkaller.appspotmail.com, Norbert Slusarek Subject: [PATCH] can: bcm: delay release of struct bcm_op after synchronize_rcu Date: Sat, 19 Jun 2021 13:18:13 -0300 Message-Id: <20210619161813.2098382-1-cascardo@canonical.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org can_rx_register callbacks may be called concurrently to the call to can_rx_unregister. The callbacks and callback data, though, are protected by RCU and the struct sock reference count. So the callback data is really attached to the life of sk, meaning that it should be released on sk_destruct. However, bcm_remove_op calls tasklet_kill, and RCU callbacks may be called under RCU softirq, so that cannot be used on kernels before the introduction of HRTIMER_MODE_SOFT. However, bcm_rx_handler is called under RCU protection, so after calling can_rx_unregister, we may call synchronize_rcu in order to wait for any RCU read-side critical sections to finish. That is, bcm_rx_handler won't be called anymore for those ops. So, we only free them, after we do that synchronize_rcu. Reported-by: syzbot+0f7e7e5e2f4f40fa89c0@syzkaller.appspotmail.com Reported-by: Norbert Slusarek Signed-off-by: Thadeu Lima de Souza Cascardo --- net/can/bcm.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/net/can/bcm.c b/net/can/bcm.c index f3e4d9528fa3..c67916020e63 100644 --- a/net/can/bcm.c +++ b/net/can/bcm.c @@ -785,6 +785,7 @@ static int bcm_delete_rx_op(struct list_head *ops, struct bcm_msg_head *mh, bcm_rx_handler, op); list_del(&op->list); + synchronize_rcu(); bcm_remove_op(op); return 1; /* done */ } @@ -1533,6 +1534,11 @@ static int bcm_release(struct socket *sock) REGMASK(op->can_id), bcm_rx_handler, op); + } + + synchronize_rcu(); + + list_for_each_entry_safe(op, next, &bo->rx_ops, list) { bcm_remove_op(op); } -- 2.30.2