From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f69.google.com (mail-wm0-f69.google.com [74.125.82.69]) by kanga.kvack.org (Postfix) with ESMTP id 3BB706B0010 for ; Mon, 7 May 2018 04:21:38 -0400 (EDT) Received: by mail-wm0-f69.google.com with SMTP id z76-v6so2289700wmh.9 for ; Mon, 07 May 2018 01:21:38 -0700 (PDT) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com. [148.163.158.5]) by mx.google.com with ESMTPS id h63-v6si1070482edd.152.2018.05.07.01.21.36 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 May 2018 01:21:36 -0700 (PDT) Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w478JJHp088835 for ; Mon, 7 May 2018 04:21:35 -0400 Received: from e06smtp14.uk.ibm.com (e06smtp14.uk.ibm.com [195.75.94.110]) by mx0a-001b2d01.pphosted.com with ESMTP id 2htj5hau88-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 07 May 2018 04:21:35 -0400 Received: from localhost by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 7 May 2018 09:21:33 +0100 Subject: Re: [PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore) From: Ravi Bangoria References: <20180417043244.7501-1-ravi.bangoria@linux.vnet.ibm.com> <20180417043244.7501-7-ravi.bangoria@linux.vnet.ibm.com> <20180504134816.8633a157dd036489d9b0f1db@kernel.org> <206e4a16-ae21-7da3-f752-853dc2f51947@linux.ibm.com> Date: Mon, 7 May 2018 13:51:21 +0530 MIME-Version: 1.0 In-Reply-To: <206e4a16-ae21-7da3-f752-853dc2f51947@linux.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Message-Id: Sender: owner-linux-mm@kvack.org List-ID: To: Masami Hiramatsu , oleg@redhat.com Cc: Ravi Bangoria , peterz@infradead.org, srikar@linux.vnet.ibm.com, rostedt@goodmis.org, acme@kernel.org, ananth@linux.vnet.ibm.com, akpm@linux-foundation.org, alexander.shishkin@linux.intel.com, alexis.berlemont@gmail.com, corbet@lwn.net, dan.j.williams@intel.com, jolsa@redhat.com, kan.liang@intel.com, kjlx@templeofstupid.com, kstewart@linuxfoundation.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, milian.wolff@kdab.com, mingo@redhat.com, namhyung@kernel.org, naveen.n.rao@linux.vnet.ibm.com, pc@us.ibm.com, tglx@linutronix.de, yao.jin@linux.intel.com, fengguang.wu@intel.com, jglisse@redhat.com Hi Masami, On 05/04/2018 07:51 PM, Ravi Bangoria wrote: > >>> +} >>> + >>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu) >>> +{ >>> + struct uprobe_map_info *info; >>> + >>> + uprobe_down_write_dup_mmap(); >>> + info = uprobe_build_map_info(tu->inode->i_mapping, >>> + tu->ref_ctr_offset, false); >>> + if (IS_ERR(info)) >>> + goto out; >>> + >>> + while (info) { >>> + down_write(&info->mm->mmap_sem); >>> + >>> + if (sdt_find_vma(tu, info->mm, info->vaddr)) >>> + sdt_update_ref_ctr(info->mm, info->vaddr, 1); >> Don't you have to handle the error to map pages here? > Correct.. I think, I've to feedback error code to probe_event_{enable|disable} > and handler failure there. I looked at this. Actually, It looks difficult to feedback errors to probe_event_{enable|disable}, esp. in the mmap() case. Is it fine if we just warn sdt_update_ref_ctr() failures in dmesg? I'm doing this in [PATCH 7]. (Though, it makes more sense to do that in [PATCH 6], will change it in next version). Any better ideas? BTW, same issue exists for normal uprobe. If uprobe_mmap() fails, there is no feedback to trace_uprobe and no warnigns in dmesg as well !! There was a patch by Naveen to warn such failures in dmesg but that didn't go in: https://lkml.org/lkml/2017/9/22/155 Also, I'll add a check in sdt_update_ref_ctr() to make sure reference counter never goes to negative incase increment fails but decrement succeeds. OTOH, if increment succeeds but decrement fails, the counter remains >0 but there is no harm as such, except we will execute some unnecessary code. Thanks, Ravi