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 7CDC0C433F5 for ; Wed, 18 May 2022 12:22:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236423AbiERMW0 (ORCPT ); Wed, 18 May 2022 08:22:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54260 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236375AbiERMWS (ORCPT ); Wed, 18 May 2022 08:22:18 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 83F135EDDB for ; Wed, 18 May 2022 05:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652876536; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=NfsVd+paNbFCf+lVJNVeNuwNcS/giE10aZS+Eiu/vhg=; b=Ev9E7FioHHNtY9gWRM74+QHVbgRvBgXDiwX7+17D5zPrFjLdLvSAsHxKowkubsG6DUhyfj DiOJbLYhzeGJvLcVVYAQZGgSJbJcA8KIP4YUe/Nkh1ZYbeAWW8Ar+lbuBA5Ifwp/NaYveg 3KkaOf4CiD+cJLOyClWKLyc/wY2xRmM= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-594-MZu_C_yEOqOFTCoJoOQEiQ-1; Wed, 18 May 2022 08:22:13 -0400 X-MC-Unique: MZu_C_yEOqOFTCoJoOQEiQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 592CC180138A; Wed, 18 May 2022 12:22:12 +0000 (UTC) Received: from asgard.redhat.com (unknown [10.36.110.4]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 016E51410DD5; Wed, 18 May 2022 12:22:08 +0000 (UTC) Date: Wed, 18 May 2022 14:22:06 +0200 From: Eugene Syromiatnikov To: Jiri Olsa , Masami Hiramatsu , Steven Rostedt , Ingo Molnar , Alexei Starovoitov , Daniel Borkmann Cc: Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH bpf v3 0/2] Fix kprobe_multi interface issues for 5.18 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello. While [1] seems to require additional work[2] due to changes in the interface (and it has already been re-targeted for bpf-next), I would like to ask to consider the following two patches, that fix possible out-of-bounds write and properly disable the interface for 32-bit compat user space, for the 5.18 release. Thank you. [1] https://lore.kernel.org/lkml/cover.1652772731.git.esyr@redhat.com/ [2] https://lore.kernel.org/lkml/YoTXiAk1EpZ0rLKE@krava/ Eugene Syromiatnikov (2): bpf_trace: check size for overflow in bpf_kprobe_multi_link_attach bpf_trace: bail out from bpf_kprobe_multi_link_attach when in compat kernel/trace/bpf_trace.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) -- 2.1.4