Received: by 2002:a05:6358:16cd:b0:dc:6189:e246 with SMTP id r13csp36097rwl; Thu, 3 Nov 2022 19:20:35 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6sTAuccnpcQTNbiFKRUGI88RwB1SrrrYX4zzcIx5HMiOo1MTCnOn7o2PmYbjvgwYdtOfq0 X-Received: by 2002:a05:6402:5211:b0:462:3a0e:cd0d with SMTP id s17-20020a056402521100b004623a0ecd0dmr33414215edd.130.1667528435192; Thu, 03 Nov 2022 19:20:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667528435; cv=none; d=google.com; s=arc-20160816; b=o3KH9/HcxvZUbqF0kAR1cf5TRP7/uVnuzhDAUdUJLZa2eXkJMKtbzvtPj753WlbL/M BCbOjggm9mXV9FZag1IVZeT3zHY4fCyd2VsLsm2m4zHZk0xSj8ZEvMZsiAmaz3ET1jbL ytzKBjaUmtifN1gNZCedOLJQpiwJKvWRfHLPDpYw/rshuZSfdQJV+K3nkdxBOFOwO+JG sahlbLu0UnXFejpMWoDqvtMMTCP/Ap0eypNZVdMX5UtDSEQd15JUpUX/1ujXgOFCem3Y hIM4MJuLmxNx4Pl3VL0g8de2e3FIG58Jd//YRVaDKnjyA92/q1bcdmq+QzH52BzXvNal gUYg== 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:from:in-reply-to :references:mime-version:dkim-signature; bh=Dkv9TmpYzRXxCdw8qjnv2btS0v4b+E/OUJk1nZvMH7U=; b=YzWGp/MKL+hhXHAYHeztyXnjOIBjmBa1B+6gwkLrRs1SAQDsP1jAuB0moM/n96gCB0 5TnVIugioXSMBW7bQXxavXTRL4C80kW1htBM43d07fYNCdzWJkY6skn9gd9AdDDtFwtE 54N6aNUBim20ThcQc54ZHEEBzBLqGVcrWHxcs4AeitIR9AQ3CLkrF04wZ34i06plFZn1 u5egqrwY7w9Jv2cT+nShgq/hWQ9Wua3joru8zHf9Rx98t3o5VZ5IWsSFcYYUjp+Qtr6R Q/KMlwkELPiXP4FL7W6i2d+ChQgaohGpWLnNEBP1Zbt4wRYf3sYzzgQI6uPXQ3BFQl5S OPng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=FhstQWOA; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m22-20020a056402051600b0045fd458991fsi2721048edv.428.2022.11.03.19.20.11; Thu, 03 Nov 2022 19:20:35 -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=@google.com header.s=20210112 header.b=FhstQWOA; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231208AbiKDB5b (ORCPT + 97 others); Thu, 3 Nov 2022 21:57:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46610 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229674AbiKDB51 (ORCPT ); Thu, 3 Nov 2022 21:57:27 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 567A523BC1 for ; Thu, 3 Nov 2022 18:57:25 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id e123so34338ybh.11 for ; Thu, 03 Nov 2022 18:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Dkv9TmpYzRXxCdw8qjnv2btS0v4b+E/OUJk1nZvMH7U=; b=FhstQWOA5IKUavuOVMM3fySx92HRbLkmJt71VxxfTzOa8jtE7NqMfyvEQGq8Shzn7j vE2AdeYUoaQU+1Rukp4DR7Z46NgQC+mAVJPQ/4qryVezyTI6KSsz06SAs1ZW6f95Sx0p 3UI6nlz5H/2WUqAvVFsdtBUKySmr3NSnSOIHSGKYFqsCF6ChYSuNSCb+yzzTryNVVJEy 4NmRyZMoxl/zdUY+2D0415X9tvhIL7pBiJWsspFeoO1FIolNIw8gtGctHEU7aGp+Xv30 kvQdnPgym7B/L85x5MIRz6npVKlfEUrmtKpZNjleSYkGEHQkNyoozPvN2X+RiKtjqGY3 Z68Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=Dkv9TmpYzRXxCdw8qjnv2btS0v4b+E/OUJk1nZvMH7U=; b=0gMglLVDw4umpPia1k8Ow1XPbQdVhuQNYUpQYC3LLoCzTNAISxRxxURRP38yifYnO0 N0wyK9+se7u19gwuT/z/GgG3Ed0j0yWziKmL3fckG78a6Jq18mqqE5H2z82wo9yv6Gxy TT0m3+AkW+ndI9JBCw6oxwFiouGL9pqYyT5LEqrY8nePMmAQyxYX9m9xUwx2KbtB+CAU ylsMVktYl0AoU/Bubeww/Vh+sd4EhGWifb7tRs/31mayAb1Fzhq1hE9805Ts20Hic2oC Vfa6ABDFHIB+8LY+pfADSsFSxMah5XV020OucG0SVSwzwsZWW/9+lhYenkVLp8ECbzoe Zvww== X-Gm-Message-State: ACrzQf2mIi0wt1B795YyeCA+ctFL746xAvIndeTw5tV9zqSJu2dIXUhU mJLEcGI9vW8BpU8PuDMEu4MJ8MmOrjVtuCEXGPtW0A== X-Received: by 2002:a25:d64e:0:b0:6cb:7faa:af94 with SMTP id n75-20020a25d64e000000b006cb7faaaf94mr32690560ybg.36.1667527044265; Thu, 03 Nov 2022 18:57:24 -0700 (PDT) MIME-Version: 1.0 References: <20221103090345.187989-1-chenzhongjin@huawei.com> <20221103165827.19428-1-kuniyu@amazon.com> <5b05c7d9-a7e3-8b32-4aa6-cd94df2858e5@huawei.com> In-Reply-To: <5b05c7d9-a7e3-8b32-4aa6-cd94df2858e5@huawei.com> From: Eric Dumazet Date: Thu, 3 Nov 2022 18:57:12 -0700 Message-ID: Subject: Re: [PATCH net] net: ping6: Fix possible leaked pernet namespace in pingv6_init() To: Chen Zhongjin Cc: Kuniyuki Iwashima , davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org, lorenzo@google.com, netdev@vger.kernel.org, pabeni@redhat.com, yoshfuji@linux-ipv6.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 Thu, Nov 3, 2022 at 6:36 PM Chen Zhongjin wrote: > > Hi, > > On 2022/11/4 0:58, Kuniyuki Iwashima wrote: > > From: Chen Zhongjin > > Date: Thu, 3 Nov 2022 17:03:45 +0800 > >> When IPv6 module initializing in pingv6_init(), inet6_register_protosw() > >> is possible to fail but returns without any error cleanup. > > The change itself looks sane, but how does it fail ? > > It seems inet6_register_protosw() never fails for pingv6_protosw. > > Am I missing something ? > > Thanks for reminding! I only injected error return value for functions > but didn't notice the inner logic. > > Rechecked and find you are right that inet6_register_protosw() is safe > for this case. > > Sorry for bothering, please reject this. Will check carefully next time. This is silly and a waste of time for many of us. If you want to send fixes for real bugs, I suggest you grab reports from syzbot queues, instead of 'injecting error values' from arbitrary functions. Thanks.