Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp2310211pxv; Sat, 26 Jun 2021 16:36:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJybbINU2IRXrxPnkznhejb1oNDSFl0ZZYQCIYkz5FRIta/hYNCSGx+rkRHuB+hH2QyQnvjE X-Received: by 2002:a02:9f05:: with SMTP id z5mr15725059jal.23.1624750588390; Sat, 26 Jun 2021 16:36:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624750588; cv=none; d=google.com; s=arc-20160816; b=tnt2CMbFpaqubfT0uXdpZn26rqSmwUHZTrHmZL1CHMpTfZFrQasgVbA9EWUhyt3iE6 bzvzyUp7s0C8iw6C3WClxqdz9xqWyYDLuPRvAQcFxGE529tMSu38/k7bz0cml4H2fVPf 76mtKXjWqGqPLmmt7wS/A+dq1YfNu62VXruhUTRWpKgl9X+Juovpy+96/nSXZWYWhF3E p5ZC7IglY0qsdO0I2IfbAN84Q7UUXJlAKeaaUiq+zlJJhKWDvlvi36Q5IPvSpdjBhT/h wONYhsCk8M12CHGIZD3U7FEWfTwWXfFz9216//tGB3bQxUCPm29zaq13/9q1quI4diEh 3SjA== 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 :references:in-reply-to:message-id:subject:cc:to:from:date; bh=m2BgC14YxNz9eU4C4Erkh/Hz8nciE62j5NDEAFJLuxA=; b=ti25QfE07U5hOkQ8OZRUUfpg+ein7sn+WKjxM3SXm9Zpt9Fy9/uU88SvEpq71dE0aX 6KzkRko6tGMLEFq1lOi51dpcNNwmrnOPIaqhlcFztusYyKkhuoLUc33nWOD8YaqWp1Wl Wv/r1YxRJQuRO8DfKRdFwvuoFzyAdHag/pXZaEhxNByYsXijCUtwtbUQliwDFCIiIvgZ 0Wp3oukGjCt4BywWhNb/Ea+ss2zjtUzJMuqzDEGLGnzzjeEb2TG4ghnnnElYPqwtUjQ3 4HGUylq9/XebHvFoSGSWra7d8n0KSwWLvhCIdTlQT7PMT8ATqgeM1YRNU8N54y43vxo4 kPhg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p16si12417430iov.2.2021.06.26.16.36.16; Sat, 26 Jun 2021 16:36:28 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230186AbhFZXiG (ORCPT + 99 others); Sat, 26 Jun 2021 19:38:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:34956 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229630AbhFZXiF (ORCPT ); Sat, 26 Jun 2021 19:38:05 -0400 Received: from rorschach.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 95F9561C45; Sat, 26 Jun 2021 23:35:41 +0000 (UTC) Date: Sat, 26 Jun 2021 19:35:40 -0400 From: Steven Rostedt To: Mathieu Desnoyers Cc: Tetsuo Handa , Peter Zijlstra , Ingo Molnar , Robert Richter , Gabriel Krisman Bertazi , "Gustavo A. R. Silva" , linux-kernel@vger.kernel.org, Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , netdev , bpf@vger.kernel.org Subject: Re: [PATCH] tracepoint: Do not warn on EEXIST or ENOENT Message-ID: <20210626193540.706da950@rorschach.local.home> In-Reply-To: <1252314758.18555.1624732969232.JavaMail.zimbra@efficios.com> References: <20210626135845.4080-1-penguin-kernel@I-love.SAKURA.ne.jp> <20210626101834.55b4ecf1@rorschach.local.home> <7297f336-70e5-82d3-f8d3-27f08c7d1548@i-love.sakura.ne.jp> <20210626114157.765d9371@rorschach.local.home> <20210626142213.6dee5c60@rorschach.local.home> <1252314758.18555.1624732969232.JavaMail.zimbra@efficios.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 26 Jun 2021 14:42:49 -0400 (EDT) Mathieu Desnoyers wrote: > > If BPF is OK with registering the same probe more than once if user > > space expects it, we can add this patch, which allows the caller (in > > this case BPF) to not warn if the probe being registered is already > > registered, and keeps the idea that a probe registered twice is a bug > > for all other use cases. > > How can removal of the duplicates be non buggy then ? The first removal will match both probes. The registering of the first duplicate would fail with an error, but will not warn. There would be no unregistering needed. -- Steve