Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2457485imu; Sat, 10 Nov 2018 15:32:09 -0800 (PST) X-Google-Smtp-Source: AJdET5dmdBg4tx+vycnfpBsOsnsV403iBcGAfDdZbdtCSAFfPoB5no4qOQ7kjuyO6+3dORrlJvqe X-Received: by 2002:a62:6881:: with SMTP id d123-v6mr14904467pfc.195.1541892729337; Sat, 10 Nov 2018 15:32:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541892729; cv=none; d=google.com; s=arc-20160816; b=BZ1ry+CbdI1dV6n3Hq8L1ZErk/jZkArEjl28V4K8wrVIAHv16uGyDG55VySVuHkznC /M7CjEcljrvMWE58uUIi65QJgiM/ZC4XKIAtlTFBvxRghrjmTNdeOVLTRAqLbHxyqqqk GcDnXIidRBzzMAb2/PhiEo71KQzRkpGTalmsO+9GYRdFoATuZD9//q6JcPovBaA40N9u QB1HDWWVKq7Aby4fO3oghRiIxfUy50loil3hKt3P6CYXB54U5hAT3aJf9cDlaJmkU5Yz 9+oZ4panvlhOo6C1PwFEYMUHw9c1zd4U2DN/qI3px0ihtmvhx1N2Zpo5lFsE8BgLxlOF M8sQ== 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=zGTcThK5HQvYSOVqouxD9DRBHafkr6p6gTXG9SLK0YE=; b=WYVYDX3w5gRZgbGJH/cPRu2S62nqX00Y5HOxRabC9n5/i/nivp3LWyfoCHIrgNee3E pnrjdeWI+2u1R7cx79YtfFEzB9PlylTI4VZJoR1mLiCaizDW2NKDU0a8Za0PIGFxhD7V tVIlC9TMctJJHKz/Nh6f6t/DhAITX/fn9FwYRFJf1Fz49y5WjGxC04J7YhNI9KYkypu3 hrnziZEOMDxbK23znJQVXxzspeD5qA6jml7B1+YhvhGNKjdK/gQhmPIydMKXHIbOMojb nMjI6UKCN+XwVE63tshi4ACbf0rYKqvFVfxkeA5DwVxcuHKEt0FvijoWYMUGcsbx6rv9 ZMrw== 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 o1si11601647pgq.13.2018.11.10.15.31.52; Sat, 10 Nov 2018 15:32:09 -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 S1726806AbeKKJQ4 (ORCPT + 99 others); Sun, 11 Nov 2018 04:16:56 -0500 Received: from mail.kernel.org ([198.145.29.99]:41512 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725896AbeKKJQ4 (ORCPT ); Sun, 11 Nov 2018 04:16:56 -0500 Received: from gandalf.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (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 5B1F920892; Sat, 10 Nov 2018 23:30:13 +0000 (UTC) Date: Sat, 10 Nov 2018 18:30:11 -0500 From: Steven Rostedt To: Alexander Popov Cc: kernel-hardening@lists.openwall.com, Kees Cook , Jann Horn , Ingo Molnar , Andy Lutomirski , Joerg Roedel , Borislav Petkov , Thomas Gleixner , Dave Hansen , Peter Zijlstra , Jan Kara , Mathieu Desnoyers , Dan Williams , Masahiro Yamada , Masami Hiramatsu , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] stackleak: Disable ftrace for stackleak.c Message-ID: <20181110183011.2290fc20@gandalf.local.home> In-Reply-To: <1541887530-16610-1-git-send-email-alex.popov@linux.com> References: <1541887530-16610-1-git-send-email-alex.popov@linux.com> 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 Sun, 11 Nov 2018 01:05:30 +0300 Alexander Popov wrote: > The stackleak_erase() function is called on the trampoline stack at the > end of syscall. This stack is not big enough for ftrace operations, > e.g. it can be overflowed if we enable kprobe_events for stackleak_erase(). Is the issue with kprobes or with function tracing? Because this stops function tracing which I only want disabled if function tracing itself is an issue, not for other things that may use the function tracing infrastructure. -- Steve