From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5F78CC77B7F for ; Wed, 3 May 2023 20:04:34 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D33F7900003; Wed, 3 May 2023 16:04:33 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id CBD33900002; Wed, 3 May 2023 16:04:33 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B5DA3900003; Wed, 3 May 2023 16:04:33 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) by kanga.kvack.org (Postfix) with ESMTP id 77D36900002 for ; Wed, 3 May 2023 16:04:33 -0400 (EDT) Received: by mail-wm1-f49.google.com with SMTP id 5b1f17b1804b1-3f178da219bso55336055e9.1 for ; Wed, 03 May 2023 13:04:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683144272; x=1685736272; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=rHU5powRCH79ePrW9PLsNOR73hzLy7pF/AR2cVrEP7A=; b=X9cvzf7QfWfANWyiwaBoFAaHPlX2qeqZu2VCK9dHuW20oD3qDZADVWlb+BtBIBdSiO 2RDzvFggR0cV7IyIeCqHDf9vzAIbh3l8EKnAha85GOqZ/85Z2kV5iHi0HZA5hxN3WCiL NDBgwTKeSBh1uBp9ZRn5IcKnZwjB9Xw2FNCu3VPxcgaMe8gKOK7zMR3TIQzUlk13qk0g Oy/vqaLM0dX473ikdNYh4d6O6S61SceyugQ5rTKI7IbtLax4XorLUr0QhjWGkIK6Mm8g jmi9mu20BH7ourolp1eZoSnL7KPbf6yac3FZz/qPtTH6UuXviA7A9ThzGyGaLUXBvIEp nt2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683144272; x=1685736272; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rHU5powRCH79ePrW9PLsNOR73hzLy7pF/AR2cVrEP7A=; b=RT3NPRnw6eHJMWaeCiaBS0kFpKbP8JOnlOPG1T6lnng6lbDsPqtBcIRDb9FxZ0VPWx UbAKnx9qlFfYXdoX/MTPHGnywxyscWvNr42s3iC44pRhmHESbh6mSiHe2mt9LInlr8O6 TB+slXFa8OeypC92R9wygHOyJJzhphlCyXPa0I2fCeFA0FbXUwBxXiYinLQRZyMBAeMM VusxDQDhVzyUgKGl2XvRqpH+wJiJyn9yNmPZP0DfnHMIQQ3UDECdqJoa8Py2Cim5sCpX SvHRSySfoVrN2NsyS6YMgVrCEq/KgRhgcqdo+3KeCdYTqWB5Zk5PiGIxMWt6oJeZVwMO rIBg== X-Gm-Message-State: AC+VfDwqexcTryBbDEzvB/ClbpjV4MnGVCjT1In5dORwSXIPIngKv75O m3KT2CtWnL1iCBjLhN9J29/rCo822gbFvOvZ3mw= X-Google-Smtp-Source: ACHHUZ7zpuOeQ2HlbzadDjdNCOqFD0VigwxXNnk7+zHC8ZwW/zidgTFIwlyp+cl7LdT9bLB6cLchW8xym2AySZY+Hm8= X-Received: by 2002:a5d:5222:0:b0:2fa:27ef:93d7 with SMTP id i2-20020a5d5222000000b002fa27ef93d7mr907489wra.42.1683144272448; Wed, 03 May 2023 13:04:32 -0700 (PDT) MIME-Version: 1.0 References: <20230501165450.15352-1-surenb@google.com> In-Reply-To: From: Andrey Ryabinin Date: Wed, 3 May 2023 22:04:21 +0200 Message-ID: Subject: Re: [PATCH 00/40] Memory allocation profiling To: Tejun Heo Cc: Kent Overstreet , Michal Hocko , Suren Baghdasaryan , akpm@linux-foundation.org, vbabka@suse.cz, hannes@cmpxchg.org, roman.gushchin@linux.dev, mgorman@suse.de, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, corbet@lwn.net, void@manifault.com, peterz@infradead.org, juri.lelli@redhat.com, ldufour@linux.ibm.com, catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de, tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, peterx@redhat.com, david@redhat.com, axboe@kernel.dk, mcgrof@kernel.org, masahiroy@kernel.org, nathan@kernel.org, dennis@kernel.org, muchun.song@linux.dev, rppt@kernel.org, paulmck@kernel.org, pasha.tatashin@soleen.com, yosryahmed@google.com, yuzhao@google.com, dhowells@redhat.com, hughd@google.com, andreyknvl@gmail.com, keescook@chromium.org, ndesaulniers@google.com, gregkh@linuxfoundation.org, ebiggers@google.com, ytcoode@gmail.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, bristot@redhat.com, vschneid@redhat.com, cl@linux.com, penberg@kernel.org, iamjoonsoo.kim@lge.com, 42.hyeyoo@gmail.com, glider@google.com, elver@google.com, dvyukov@google.com, shakeelb@google.com, songmuchun@bytedance.com, jbaron@akamai.com, rientjes@google.com, minchan@google.com, kaleshsingh@google.com, kernel-team@android.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux.dev, linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-modules@vger.kernel.org, kasan-dev@googlegroups.com, cgroups@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, May 3, 2023 at 6:35=E2=80=AFPM Tejun Heo wrote: > > Hello, Kent. > > On Wed, May 03, 2023 at 04:05:08AM -0400, Kent Overstreet wrote: > > No, we're still waiting on the tracing people to _demonstrate_, not > > claim, that this is at all possible in a comparable way with tracing. > > So, we (meta) happen to do stuff like this all the time in the fleet to h= unt > down tricky persistent problems like memory leaks, ref leaks, what-have-y= ou. > In recent kernels, with kprobe and BPF, our ability to debug these sorts = of > problems has improved a great deal. Below, I'm attaching a bcc script I u= sed > to hunt down, IIRC, a double vfree. It's not exactly for a leak but leaks > can follow the same pattern. > For leaks there is example bcc https://github.com/iovisor/bcc/blob/master/tools/memleak.py