Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp379708imj; Sat, 16 Feb 2019 02:25:40 -0800 (PST) X-Google-Smtp-Source: AHgI3Iap2HMl2bjfBrD+lzC1nkaMtCx+3RKXTj8Fpse3ODg1TjBsu9RMbDjEy42/83jX9bgnBuAw X-Received: by 2002:a63:81c1:: with SMTP id t184mr9156111pgd.228.1550312740237; Sat, 16 Feb 2019 02:25:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550312740; cv=none; d=google.com; s=arc-20160816; b=mJm33EaIKWWdvTKFztV35+Vgated/lvfrc9k7zeYjW9XBWW13hXtXZuGd4a4nw0dMZ 0Zs6sBUWOrMgGMuRTI6m9WcFyolfrwwad6VuD22FuCLbhMsVN7J9IE7lLxOesMvTTyYd VLXN/FurbislAWSsCPGRG5+aCkXMagglNoecMRHMmkEA96RaVIQ7NdIonZd4KHM0jl3q 5K3BKCoWjGIcqrBJiC8PH/jBQQrVD1tl0xe1u+kc3euz/qxfY4t3U1ZGm+W/fJNuYpe9 gdha7kLGCNI1Sut22uE09z3zW22oiUntgLrKcjuDxqkdVq7pq+xSGPiWjkS/NEN2Hryz 87SQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=RKmMJtsF3XNpAPMrYe50Y7QiOP2s8HYv/vKdULzfsNE=; b=aPOnou3otzT6zh1OjoP5a47fSr/t7d/YYB3GCPLFaEbx9QkYjsiELoW6JAxYMxYyZu e/CLWdxx7U476n8sXgJkUJ9z/e5NbemMhowx2FOJrOKaDolocBEhqV0DirCp3K0PnxEE W8SFzwJ4vXa5o1DwscD90f4Dz39+wmjvRM7I1+NiwMFTXZQiFQuVqcX8ywO5ilOih0Be 8OGyNH+ARCzvSAIhptG2z+f5rI8SkiVeISip5SWcgrqTpUyyoGXwh2ITv5hQbKjA3zsq fHBAyFWN57pv/mOqek4cBhSY92fQEHgDi4VKJQbI/PnQiLnuqqHfCSPidIdsx8hf1QQ6 g13Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s12si7414908pfm.242.2019.02.16.02.25.23; Sat, 16 Feb 2019 02:25:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389661AbfBPCVg (ORCPT + 99 others); Fri, 15 Feb 2019 21:21:36 -0500 Received: from mail.kernel.org ([198.145.29.99]:44274 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727348AbfBPCVf (ORCPT ); Fri, 15 Feb 2019 21:21:35 -0500 Received: from gandalf.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 690B0222D0; Sat, 16 Feb 2019 02:21:34 +0000 (UTC) Date: Fri, 15 Feb 2019 21:21:33 -0500 From: Steven Rostedt To: Andy Lutomirski Cc: Linus Torvalds , Linux List Kernel Mailing , Ingo Molnar , Andrew Morton , stable , Changbin Du , Jann Horn , Kees Cook , Andy Lutomirski Subject: Re: [PATCH 1/2 v2] kprobe: Do not use uaccess functions to access kernel memory that can fault Message-ID: <20190215212133.7d33444f@gandalf.local.home> In-Reply-To: <1B52384E-5C02-4279-9111-34881BA3204E@amacapital.net> References: <20190215174712.372898450@goodmis.org> <20190215174945.557218316@goodmis.org> <20190215171539.4682f0b4@gandalf.local.home> <300C4516-A093-43AE-8707-1C42486807A4@amacapital.net> <20190215191949.04604191@gandalf.local.home> <20190215210801.7f8c94cf@gandalf.local.home> <1B52384E-5C02-4279-9111-34881BA3204E@amacapital.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 15 Feb 2019 18:14:21 -0800 Andy Lutomirski wrote: > > In the uprobes case, we have: > > > > static nokprobe_inline int > > probe_mem_read(void *dest, void *src, size_t size) > > { > > void __user *vaddr = (void __force __user *)src; > > > > return copy_from_user(dest, vaddr, size) ? -EFAULT : 0; > > } > > > > Because that is adding probes on userspace code. > > > > > > Can the kprobe case call probe_kernel_read? Maybe it does already? Yes, the probe_mem_read() is only used in the trace_probe_tmpl.h which for uprobes is the above "copy_from_user()" and for the kprobes case it is probe_kernel_read(). -- Steve