From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B876CC433FE for ; Tue, 8 Mar 2022 14:50:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347607AbiCHOvM (ORCPT ); Tue, 8 Mar 2022 09:51:12 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44090 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234882AbiCHOvK (ORCPT ); Tue, 8 Mar 2022 09:51:10 -0500 Received: from sin.source.kernel.org (sin.source.kernel.org [145.40.73.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B21923916C; Tue, 8 Mar 2022 06:50:13 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id E6213CE16C0; Tue, 8 Mar 2022 14:50:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 12346C340F4; Tue, 8 Mar 2022 14:50:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1646751010; bh=a7oTzDNK1Df7u0KQ+Jv0WvIy358t9zua3Q7ZJYXsXjw=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=Yj/6ePDQXHp4QyGJ40Imt/MLuwjVLLK7SHgLpxFmMFn9AxNqdxP4xs2WAtq0KgTFe Spuo83ArJFC600uYHD4V8JRFK4xdm7y8WsjkLCMb75pjLVfKkxNC8zknyA/MqMy+wa Tk6spzRgifgFJq5ccx4IKx95/LwTvz3tD3Re6VJ2aqy46RJQ1ZXL2qZY6Kd010paQ/ Q5brqSzUJPt/av95WQ57gWz/Nk7zkiBWbA53UVLJQ/1q2YSFRSI3Hh0lMRaiPQtprM fC+BK76GRkvzfgwNrtfFPjlaAShTBZtr9uPaZy4eBirb9Mlfa6a3dYW3GPi77BYgTO SH3b/B/EKBVJw== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id DA236E6D3DD; Tue, 8 Mar 2022 14:50:09 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH bpf-next] bpf: determine buf_info inside check_buffer_access() From: patchwork-bot+netdevbpf@kernel.org Message-Id: <164675100988.18270.17850383970446997392.git-patchwork-notify@kernel.org> Date: Tue, 08 Mar 2022 14:50:09 +0000 References: In-Reply-To: To: Shung-Hsi Yu Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com, songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, netdev@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to bpf/bpf-next.git (master) by Daniel Borkmann : On Mon, 7 Mar 2022 13:29:18 +0800 you wrote: > Instead of determining buf_info string in the caller of > check_buffer_access(), we can determine whether the register type is read-only > through type_is_rdonly_mem() helper inside check_buffer_access() and construct > buf_info, making the code slightly cleaner. > > Signed-off-by: Shung-Hsi Yu > > [...] Here is the summary with links: - [bpf-next] bpf: determine buf_info inside check_buffer_access() https://git.kernel.org/bpf/bpf-next/c/44e9a741cad8 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html