Received: by 2002:ac0:b08d:0:0:0:0:0 with SMTP id l13csp2987485imc; Sat, 23 Feb 2019 16:46:28 -0800 (PST) X-Google-Smtp-Source: AHgI3IboQXIFbeM8ydVFoxqAjSN7cYJ/oJ10VpUYgI0EYHqQs85n2S5KU6jVeijz9Dq6xd9HFsuT X-Received: by 2002:a63:6605:: with SMTP id a5mr10988377pgc.372.1550969188395; Sat, 23 Feb 2019 16:46:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550969188; cv=none; d=google.com; s=arc-20160816; b=JwSgdbjaOFXs/R/QuH54WZr+JC3dc2tTEQR5iaAUIZreJrCansQ+H40hOb0y6quoN0 UEdx6+DYcEQdJbKAhuuYcDC8MnIJbHshKX9EfRgUUllkwGDKnX8aZOFQTbm5qcAJ1e6+ xVd201YSLjc8k/YXTGDtzJ3/HrFWb9FMSxYhYJDcDUl5OfnUSNPfvAt0HbB87APK8s37 0SS72uZ97tTlmihzIadk5WYJ76KUlOiDuKm5Go1tCY33FKrRzx6eoFTTRQLp0YvQctIl 0noHlX3YFuy00IeKp/PCAMfnRXHroIUXymDiEIZoQLFrQ6/6Dy5bepyLCDI7aYoaQWcB yzKw== 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=aRiuZHlnBsix3xoT3Bierf3fGrSIkrXILXd8s2T2GKk=; b=mxkqNPlBnsbBD3QmIkAIkMiwzOFW/U8EnlmEFzArV0Psj1dXvh0hKhFgJC7v4zKgo5 0UXIj1/vviO64AiIklfKACXCqd9+VNu/qkGqh5/pvsHDS62TqB5H4SpjLsRpDo/cNSd3 HExKDDe1SJo8Lmt4p9ad7R+h5fHIunQdXAh8dIz9Wl7c/N0tDEpoh/dNiqz6vfmq1k8J c6oU3y8BI8/InN7gqZZGzeEniRo5z7H4tjCKN3rLaBlWp2rJ7DV6ZxvX3VSzDW7QecrF 8zPqO+cDDtXmXA4fMgiP9wgt9NUuFxhHrRxL626GbzmNg0z2bMpHwfmUm08iBTQTfh/d BWBg== 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 f22si4552983pgv.578.2019.02.23.16.45.35; Sat, 23 Feb 2019 16:46:28 -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 S1728032AbfBXAo0 (ORCPT + 99 others); Sat, 23 Feb 2019 19:44:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:60464 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727800AbfBXAo0 (ORCPT ); Sat, 23 Feb 2019 19:44:26 -0500 Received: from oasis.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 65B5E20855; Sun, 24 Feb 2019 00:44:24 +0000 (UTC) Date: Sat, 23 Feb 2019 19:44:21 -0500 From: Steven Rostedt To: Masami Hiramatsu Cc: Linus Torvalds , Andy Lutomirski , 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: <20190223194421.725a03fd@oasis.local.home> In-Reply-To: <20190223124746.d021973004c7c892c3b3fde1@kernel.org> 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> <20190219111802.1d6dbaa3@gandalf.local.home> <20190219140330.5dd9e876@gandalf.local.home> <20190220171019.5e81a4946b56982f324f7c45@kernel.org> <20190220094926.0ab575b3@gandalf.local.home> <20190222172745.2c7205d62003c0a858e33278@kernel.org> <20190222173509.88489b7c5d1bf0e2ec2382ee@kernel.org> <20190223124746.d021973004c7c892c3b3fde1@kernel.org> X-Mailer: Claws Mail 3.17.3 (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 Sat, 23 Feb 2019 12:47:46 +0900 Masami Hiramatsu wrote: > Since kprobes handler runs in IRQ context, we can not use access_ok() in it. > (only on x86 + CONFIG_DEBUG_ATOMIC_SLEEP=y) Is it really IRQ context or exception context? That is, one (interrupts) happen for any task, but exceptions happen because of the software that is executed (like a breakpoint). Although you can have a kprobe trigger in an interrupt handler (where user access wouldn't make sense anyway). But there should be no problem with user access from an exception handler. -- Steve