Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 27 Oct 2020 10:58:10 -0700
From:   "Paul E. McKenney" <paulmck@kernel.org>
To:     elver@google.com, dvyukov@google.com
Cc:     linux-kernel@vger.kernel.org, andriin@fb.com
Subject: Recording allocation location for blocks of memory?
Message-ID: <20201027175810.GA26121@paulmck-ThinkPad-P72>
Reply-To: paulmck@kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

Hello!

I have vague memories of some facility some time some where that recorded
who allocated a given block of memory, but am not seeing anything that
does this at present.  The problem is rare enough and the situation
sufficiently performance-sensitive that things like ftrace need not apply,
and the BPF guys suggest that BPF might not be the best tool for this job.

The problem I am trying to solve is that a generic function that detects
reference count underflow that was passed to call_rcu(), and there are
a lot of places where the underlying problem might lie, and pretty much
no information.  One thing that could help is something that identifies
which use case the underflow corresponds to.

So, is there something out there (including old patches) that, given a
pointer to allocated memory, gives some information about who allocated
it?  Or should I risk further inflaming the MM guys by creating one?  ;-)

							Thanx, Paul