Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp4033729rwl; Tue, 28 Mar 2023 01:22:49 -0700 (PDT) X-Google-Smtp-Source: AKy350b+Z4+QJPudfmvuQkYiBX/JEkDqPINNG2PjzEYH9r8QuKSdTtnq5saSlqpLbVPuhSaR0owm X-Received: by 2002:a17:906:a24f:b0:931:bc69:8f94 with SMTP id bi15-20020a170906a24f00b00931bc698f94mr15508879ejb.45.1679991769034; Tue, 28 Mar 2023 01:22:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679991769; cv=none; d=google.com; s=arc-20160816; b=tu2SeSERchLdQb7dKg9ArI1BPtQxoPaVQwy86W7rOd76htr8IkuEb6zDurQRMlq0d4 VgUkUYXhfuirPlb5MMkkcEgNyrn5i/lsxgHbyMqdnJcJPkHlCBpcsLGL77Lzvj0pqt4M RL6ZLCkyyRn0C4ZcpP7xDgbpNdY2oorBrE4+HDLGdU62r36thVJgj9ZRJV6pWm+tF0RT +0CR7mFQjPJtKs0J72pwA8yh7fZv8iTd/JLg6rbqlmoLEPJ3NeCDy2fxOUyHonzOebP+ Y7RHuWv/DS8dESA7hrpRhcGQy5GZy3HYSJqw36m8zC/QIgQwxKgjpy2SpXUYie1uIwwN SYZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=yr41f9OaW6GBOKNvZ668MEYtnEem+75Xrjr4jNlL+ts=; b=ceWQJXYeHxWBggkKefCGztlNpSGC82mHb0oKcsHx/rZvFMXsSdWeJdLVUxfhZgMR5U KDBJvyhhNKRwQvDgXqr8uywSsXtcN0EQdPRf8bBJxYag5JdP+fAgpISIPZAnp2pOTu3Y AjtBgHcwH7gXblmUKmqb/9FtdZQ81YShYRkwrR8U67NA/91wjQBH233Wt5B+axt07MYI 8kcgvdUnPB1NIRL8ociykE1fW99ftKuHz/JhFFcho7me1ATmrtRsM5A64Ytw14/rL2fN 58aeL2osgQLkASNF5ybj2QH86wtWEW7eLWjt3zRbX5FDu0dliqMkJ3IMVZmEW+ml8WQC m/tA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=Q7GndPER; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a26-20020a1709064a5a00b00931038178ecsi24619697ejv.330.2023.03.28.01.22.33; Tue, 28 Mar 2023 01:22:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-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=@sipsolutions.net header.s=mail header.b=Q7GndPER; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229789AbjC1ITF (ORCPT + 60 others); Tue, 28 Mar 2023 04:19:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36864 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230167AbjC1ITC (ORCPT ); Tue, 28 Mar 2023 04:19:02 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9CB84C27; Tue, 28 Mar 2023 01:18:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=yr41f9OaW6GBOKNvZ668MEYtnEem+75Xrjr4jNlL+ts=; t=1679991534; x=1681201134; b=Q7GndPERV1JfPEhUFMLEmAUbczc1Xgu8oQfZahJQ9yWPoVL K+HTPs5cQFuwUuyyXH2Iu05lMX1tJpuBK7wruW3Bs/igk9wpgQkXCXowwGE5ueXATKdpVquXTNXHj mDZ4IAIPOhgJqw5E/Lix4YSQuY7gHIHGuLd5tcKdcIu+lN3Jat0lhfUpxgjno8zxapPxCJ4zeQb9n zdxsZw1Jn5Ry57LW81NkkQ5sNglIICtSMryhFBIEXApOKD+0QFdsXC1Zai4zjB2Ycjq8cUCs8xVJ+ RB4c4883/0AREcxcFLBWw7AT21vZ7S5r3qCUYV4jzvZdBsmIb/mCjQxVyam3bkuA==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1ph4Xc-00Gbrk-0o; Tue, 28 Mar 2023 10:18:52 +0200 Message-ID: Subject: Re: traceability of wifi packet drops From: Johannes Berg To: Eric Dumazet Cc: Jakub Kicinski , netdev@vger.kernel.org, linux-wireless@vger.kernel.org Date: Tue, 28 Mar 2023 10:18:51 +0200 In-Reply-To: References: <00659771ed54353f92027702c5bbb84702da62ce.camel@sipsolutions.net> <20230327180950.79e064da@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS 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-wireless@vger.kernel.org On Tue, 2023-03-28 at 01:16 -0700, Eric Dumazet wrote: >=20 > About visibility: Even before 'drop reasons' developers can always use > the call graph . >=20 > perf record -a -g -e skb:kfree_skb ... Yeah, except right now it doesn't work in mac80211 because we have these "RX handlers" that just return a status, and then a single place drops the skb. > Really drop reasons are nice when you want filtering and convenience. > But they are a lot of work to add/maintain. > This all comes at a cost (both maintenance but also run time cost > because we need to propagate reasons ) Right ... I don't think the runtime cost would be much of an issue here (we just get them as a return value from one function to pass to kfree_skb), but the maintenance is hard. I guess we could also restructure the code to call kfree_skb() in all those places that want drop it and then we have the call trace, but I doubt that would actually be cheaper both in the maintenance sense (always need to pay attention to it) or in the runtime sense. johannes