Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp246672rwb; Tue, 25 Jul 2023 15:17:39 -0700 (PDT) X-Google-Smtp-Source: APBJJlGQsVhAQgFFo+xmx1dyAx2+XNHHwR5uveVEIDml5Ba4DIch/hmwpc54pvx/g9tztLvFXtiF X-Received: by 2002:a2e:a0d4:0:b0:2b6:d838:1931 with SMTP id f20-20020a2ea0d4000000b002b6d8381931mr75565ljm.30.1690323458900; Tue, 25 Jul 2023 15:17:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690323458; cv=none; d=google.com; s=arc-20160816; b=LGH3UN99SJxEaaMWOacXMK0z+Y5S7C47lh2Q0sPuxBli4hLtJvUcACIQnn/henC/ds oCa/MQqGTezBCv+BkWP9rfnHz496ASTN1NygZH7e6wnNTolYH+sWyxOpDrocKVzWRIfZ eLGNKAfnEN2FwjQEZSmJ1b0yJ+mzZgxQwKJzAN7P/rqjdNisv0f0PXhytMXJlHaGJaM+ 8ssd0Ts7hhksNrqpL21gu++CvBd2HP3fzIu7d0gICB5i9aGnMomGPC8nd3IeV3iAPA0w /sirRSI9QdAYctjzdV4bxXDHNfIGXJJb76RCN6szjtCQO0denIX5977KwDxvVwS/VvGs Cwrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=volTAAeL8fKmMhSVDeFyV0ZoI3X0kFdQ4vEkodcC4os=; fh=332qkSqQvcO1AyV7ANanbylBxR35SpNd6PIndZ/eROk=; b=RhSC57bm4hTlRtYXsI7suEcTO8y0vi0/PU+4ulZqxyKFh1hsUhPoUQUMARK7e6dRBf cSRK9vNqyhs374RK5KC0/MdWJ+TVctu84shcagVkHn4vtpVnFj9OMPdvfgrYzp+xkFv3 5tbb6ZJIX4XXt8ltnuVfl4zLWKU0Ljj79EWcvM1rZsTWshIu242RsGLoHAQXH1uCTUwi nYBGhNJbJt1t+ei0vzwOR23bi4BOrRSFDcHn1/n3HZFdETiPSJK+G4AU8DJzdHWoL013 uNxD2KpD8NlKmRBYUIZHXVYRnpBkl1rTGEHX5A5Q6hTU0aaPE7Xp0gj2jlwUs79Denlr q5cA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=aPfoBPRn; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id rk3-20020a170907214300b00992c195ac80si8826899ejb.357.2023.07.25.15.17.12; Tue, 25 Jul 2023 15:17:38 -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=@gmail.com header.s=20221208 header.b=aPfoBPRn; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231601AbjGYV4E (ORCPT + 99 others); Tue, 25 Jul 2023 17:56:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44886 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231169AbjGYV4D (ORCPT ); Tue, 25 Jul 2023 17:56:03 -0400 Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59A8A1FE6; Tue, 25 Jul 2023 14:56:02 -0700 (PDT) Received: by mail-vk1-xa2d.google.com with SMTP id 71dfb90a1353d-4814bea10e0so2241347e0c.1; Tue, 25 Jul 2023 14:56:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690322161; x=1690926961; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=volTAAeL8fKmMhSVDeFyV0ZoI3X0kFdQ4vEkodcC4os=; b=aPfoBPRnQhWQ2T9EzFVNum8zlrhaNbwkP4cUQoofLJYJ24jlKvcUpTEGPl73BvsB9w +/wHawbHaVoRAqXAkoe+e7N66jWegqcpCGhGHfNmjbJLP7kegofOmRNSFuKPzLv1r5zS 7asIYDgODM0udnr1i6GkFY4SunbJDIb2EL2RmnMMnOPrnyRBdtL5orw+SndgAY665wbk UKCVx5iZgohjHdehGk6plJKSDdRd7V0qKw/RrGfrbF66UvUWtU5BhVr3YRy0peF/wO5Z aeo1JOB8VDhT3z56HaSBfIdX0lczj2PXON82KA8ywR6WaNv0kZLT3OZJK9Tukqwz81oP aL4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690322161; x=1690926961; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=volTAAeL8fKmMhSVDeFyV0ZoI3X0kFdQ4vEkodcC4os=; b=VZ4ZLDzFak9nER4UjbzCvWsmAiP+4PZf/uqF1gCXKCKyNhj/LL61OzUVjJV8yGcpFr vybSXGC4Hy7+WZM517Yblih3EunRMLED9ouw6p5CFxecUXGfPCjjh9fDdkCHnW3OH3AR 3EAZ+FVdZKoWaEVy1v/aZ//w9QssILzYXeI20BG3JvQRMyd9ij541gdPypBRBa4O8ta2 Vq1Z/qiyxpEzsXMvpHkKiI5j6XS4jWL87NIjE/xE5md3iH/ao4gSWO/GCXckibIqu5ih +I8xMpUIaEuNf4a9seHgKwhSHgVNkIHeOi2qHBdrvl4qI4NSP/yt4E0EQRoj1nti8GNI vU9Q== X-Gm-Message-State: ABy/qLbh8jrQ61FyrYCllSTvQDWzgCGGNTcYPDJFwSgiWcCnHsBWimna PxVBY/ImNZjGVuNzREISjiXX4ZflCRmCjzFBouq7ak/f+Co= X-Received: by 2002:a1f:45c9:0:b0:486:3e05:da14 with SMTP id s192-20020a1f45c9000000b004863e05da14mr372750vka.12.1690322161172; Tue, 25 Jul 2023 14:56:01 -0700 (PDT) MIME-Version: 1.0 References: <20230725214628.25246-1-pchelkin@ispras.ru> In-Reply-To: <20230725214628.25246-1-pchelkin@ispras.ru> From: Xin Long Date: Tue, 25 Jul 2023 17:55:39 -0400 Message-ID: Subject: Re: [PATCH v2] tipc: stop tipc crypto on failure in tipc_node_create To: Fedor Pchelkin Cc: Jon Maloy , Ying Xue , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org, Alexey Khoroshilov , lvc-project@linuxtesting.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 25, 2023 at 5:46=E2=80=AFPM Fedor Pchelkin = wrote: > > If tipc_link_bc_create() fails inside tipc_node_create() for a newly > allocated tipc node then we should stop its tipc crypto and free the > resources allocated with a call to tipc_crypto_start(). > > As the node ref is initialized to one to that point, just put the ref on > tipc_link_bc_create() error case that would lead to tipc_node_free() be > eventually executed and properly clean the node and its crypto resources. > > Found by Linux Verification Center (linuxtesting.org). > > Fixes: cb8092d70a6f ("tipc: move bc link creation back to tipc_node_creat= e") > Suggested-by: Xin Long > Signed-off-by: Fedor Pchelkin > --- > v1->v2: simplify the patch per Xin Long's advice: putting the ref on erro= r > case would solve the problem more conveniently; update the patch > description accordingly. > > net/tipc/node.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/net/tipc/node.c b/net/tipc/node.c > index 5e000fde8067..a9c5b6594889 100644 > --- a/net/tipc/node.c > +++ b/net/tipc/node.c > @@ -583,7 +583,7 @@ struct tipc_node *tipc_node_create(struct net *net, u= 32 addr, u8 *peer_id, > n->capabilities, &n->bc_entry.inputq1, > &n->bc_entry.namedq, snd_l, &n->bc_entry= .link)) { > pr_warn("Broadcast rcv link creation failed, no memory\n"= ); > - kfree(n); > + tipc_node_put(n); > n =3D NULL; > goto exit; > } > -- > 2.41.0 > Reviewed-by: Xin Long