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 X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6C50BC55178 for ; Thu, 5 Nov 2020 19:30:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 03E7A20867 for ; Thu, 5 Nov 2020 19:30:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=dxuuu.xyz header.i=@dxuuu.xyz header.b="L0XhRdyV"; dkim=temperror (0-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="HipFs0T3" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732241AbgKETaB (ORCPT ); Thu, 5 Nov 2020 14:30:01 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:52197 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727851AbgKETaA (ORCPT ); Thu, 5 Nov 2020 14:30:00 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D7EC55C0194; Thu, 5 Nov 2020 14:29:58 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 05 Nov 2020 14:29:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dxuuu.xyz; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm1; bh=/EbwIVqAd4S4jxZr8erVVHn5BX H6AogaRJ+OMfzsmRw=; b=L0XhRdyVJWhvyKg23AtwxYQdTHm8RNigjpZXyE6IEj hykLHdDuqqRVxwB33qEu2+W555OE4bktMCSVaiKm2wGhS+vA7lN1LIBzwdwcpC5R S13/OeHEi/4ZVfZVZj+bRvYDLAi459RldX5v7dljYYoSAHnCquoxx/O560AqmfVa M+WlrwMzw3+4RrkSFnARNhnROvdNcDzbwu5l/w5eWNMeGZx3G1F4tZzeRatxU8c5 Pp0B8+p3DbUoJzg5Ugv4Q5mSC/7bj+SnCWzhZ11Ck20H0MxhfiiobsoQ59wStilq FdW5EXw9XUfTnOHKUH11s/nbD4JWLVjY97peKnqi9Qkg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/EbwIVqAd4S4jxZr8 erVVHn5BXH6AogaRJ+OMfzsmRw=; b=HipFs0T33qLV23+ExL2BrYLKuCJUesOG2 hVQNePfDW3gL8jyTbOCJGSY6/ohIOG9SdPBiE6kSCxHaPcc4opCMN32IVUGL0rfr ArF6lkMJarBAcFsUR8gHVNR7skyPX9MBtIE2DoV8iip345u368G07csH71ayDyp2 ILD9mK1tPsrfcEc2dhf6MMfzdbFRGrT2aTT9ifbztfHjdVCdlO9oq8zsd+Qizlb9 /vYCNJLKV0YC2LeuTmpv3U12QteKW/mDeMDhjVJ+yVGEB6il55jhMDs+RgDK4NxZ uRq25GghE5l+pziobYSpRuTCmWWWfh76WHSi04zO1pzyKvTo4Ei5w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddtjedguddvhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhephf fvufffkffoggfgsedtkeertdertddtnecuhfhrohhmpeffrghnihgvlhcuighuuceougig uhesugiguhhuuhdrgiihiieqnecuggftrfgrthhtvghrnhepieffgfelvdffiedtleejvd etfeefiedvfeehieevveejudeiiefgteeiveeiffffnecukfhppeeiledrudekuddruddt hedrieegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epugiguhesugiguhhuuhdrgiihii X-ME-Proxy: Received: from localhost.localdomain (c-69-181-105-64.hsd1.ca.comcast.net [69.181.105.64]) by mail.messagingengine.com (Postfix) with ESMTPA id 6900A3280391; Thu, 5 Nov 2020 14:29:57 -0500 (EST) From: Daniel Xu To: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net, songliubraving@fb.com Cc: Daniel Xu , kernel-team@fb.com Subject: [PATCH bpf v3 0/2] Fix bpf_probe_read_user_str() overcopying Date: Thu, 5 Nov 2020 11:29:20 -0800 Message-Id: X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 6ae08ae3dea2 ("bpf: Add probe_read_{user, kernel} and probe_read_{user, kernel}_str helpers") introduced a subtle bug where bpf_probe_read_user_str() would potentially copy a few extra bytes after the NUL terminator. This issue is particularly nefarious when strings are used as map keys, as seemingly identical strings can occupy multiple entries in a map. This patchset fixes the issue and introduces a selftest to prevent future regressions. v2 -> v3: * set pid filter before attaching prog in selftest * use long instead of int as bpf_probe_read_user_str() retval * style changes v1 -> v2: * add Fixes: tag * add selftest Daniel Xu (2): lib/strncpy_from_user.c: Don't overcopy bytes after NUL terminator selftest/bpf: Test bpf_probe_read_user_str() strips trailing bytes after NUL lib/strncpy_from_user.c | 9 ++- .../bpf/prog_tests/probe_read_user_str.c | 60 +++++++++++++++++++ .../bpf/progs/test_probe_read_user_str.c | 34 +++++++++++ 3 files changed, 101 insertions(+), 2 deletions(-) create mode 100644 tools/testing/selftests/bpf/prog_tests/probe_read_user_str.c create mode 100644 tools/testing/selftests/bpf/progs/test_probe_read_user_str.c -- 2.28.0