Received: by 10.192.165.156 with SMTP id m28csp88381imm; Tue, 10 Apr 2018 17:04:30 -0700 (PDT) X-Google-Smtp-Source: AIpwx48k+9j7dOL7d3e8CQKf6FAD/nuraqLB1EtRBTTJd0Qpn0Rg82DbitVCae8sQpiVvgkKYHtT X-Received: by 10.99.143.30 with SMTP id n30mr1771437pgd.213.1523405070744; Tue, 10 Apr 2018 17:04:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523405070; cv=none; d=google.com; s=arc-20160816; b=llwquug5UltvdkLxXbzOxeMwUyPr7dX5lHALgW3TSu5SUqL+RoZ9lJAxPKRNwyw5jr x7ig0Ki9Tm+yyoZlD/5ZeMPJ/87eysoeVepLZjrRY47i8XHCBuM9S9xQ3HYprOc5cb0w VWbtuDj0UhX4Zt/aV8NrM1DCRVppFoct9MQvdvb9WgAriX0ZkdByAzFZgBY89uQ5XMv8 tFJqAtYkb7h21cH0Tzpx/sklcTXE7BNSA7qhMwQdwrxUdP3nnVKOrycg+9PC2Rzs69TW HoE5kS5Vz76K8n0HCqEAv2GxBB7xFamjZsfHQ89w6OaKfgux7TksuKnFgda8/M57f0qx xzMA== 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 :dmarc-filter:arc-authentication-results; bh=DEWPbwfM/9XRyykl29E9Dri31VuiqjfKcB5eKIDiEHQ=; b=WYarLinJoyGo9hYvf+kE+d5S2CXUIIlbfE8UjTcX4Co+vi/4Ah12AAYfy9b618WWMB ajYWSwWVwdRCRdk7Q7R/mWfcnqvr/2eX9ebWh36vr/9E9Jm8RlTkHkuusjBVOr/lQoCA jjUKoU0759RxIZQ+cT+o+VgXjU+qupFIsZxpgOD2NY5TU1uUZhXj52cP7F6q7wI97Iz/ RQek0JmWQcjpeyZvcd6GuHqpxGV8vB2XSIDFxXETk2E2SgKROhaK/DRrFf99FnbNDnl0 JcAr+dli5I+vo/wD51QVEmyAajrAAmqQtp7YLw/joN9ew/jq7hJm8+rUau2Q3afDui+4 QylA== 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 r59-v6si3591760plb.218.2018.04.10.17.03.53; Tue, 10 Apr 2018 17:04:30 -0700 (PDT) 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 S1752265AbeDKABE (ORCPT + 99 others); Tue, 10 Apr 2018 20:01:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:59594 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751960AbeDKABD (ORCPT ); Tue, 10 Apr 2018 20:01:03 -0400 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 E6DFE21722; Wed, 11 Apr 2018 00:01:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E6DFE21722 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Tue, 10 Apr 2018 20:00:59 -0400 From: Steven Rostedt To: Howard McLauchlan Cc: , Ingo Molnar , , Masami Hiramatsu , Srikar Dronamraju Subject: Re: [PATCH] uprobe: add support for overlayfs Message-ID: <20180410200059.731d87fe@gandalf.local.home> In-Reply-To: <20180410231030.2720-1-hmclauchlan@fb.com> References: <20180410231030.2720-1-hmclauchlan@fb.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 Tue, 10 Apr 2018 16:10:30 -0700 Howard McLauchlan wrote: > uprobes cannot successfully attach to binaries located in a directory > mounted with overlayfs. > > To verify, create directories for mounting overlayfs > (upper,lower,work,merge), move some binary into merge/ and use readelf > to obtain some known instruction of the binary. I used /bin/true and the > entry instruction(0x13b0): > > $ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work merge > $ cd /sys/kernel/debug/tracing > $ echo 'p:true_entry PATH_TO_MERGE/merge/true:0x13b0' > uprobe_events > $ echo 1 > events/uprobes/true_entry/enable > > This returns 'bash: echo: write error: Input/output error' and dmesg > tells us 'event trace: Could not enable event true_entry' I tried the above and verified that it is a problem and your patch solves it. Thanks, I'll apply it and start my tests on it. -- Steve > > This change makes create_trace_uprobe() look for the real inode of a > dentry. In the case of normal filesystems, this simplifies to just > returning the inode. In the case of overlayfs(and similar fs) we will > obtain the underlying dentry and corresponding inode, upon which uprobes > can successfully register. > > Running the example above with the patch applied, we can see that the > uprobe is enabled and will output to trace as expected. > > Reviewed-by: Josef Bacik > Signed-off-by: Howard McLauchlan > --- > kernel/trace/trace_uprobe.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c > index 2014f4351ae0..17c65fa4136d 100644 > --- a/kernel/trace/trace_uprobe.c > +++ b/kernel/trace/trace_uprobe.c > @@ -446,7 +446,7 @@ static int create_trace_uprobe(int argc, char **argv) > if (ret) > goto fail_address_parse; > > - inode = igrab(d_inode(path.dentry)); > + inode = igrab(d_real_inode(path.dentry)); > path_put(&path); > > if (!inode || !S_ISREG(inode->i_mode)) {