From: Vlastimil Babka <vbabka@suse.cz>
To: Maninder Singh <maninder1.s@samsung.com>,
paulmck@kernel.org, linux@armlinux.org.uk, cl@linux.com,
penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, 0x7f454c46@gmail.com,
viro@zeniv.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
a.sahrawat@samsung.com, Vaneet Narang <v.narang@samsung.com>
Subject: Re: [PATCH 2/3] mm/slub: Add Support for free path information of an object.
Date: Thu, 18 Mar 2021 13:35:37 +0100 [thread overview]
Message-ID: <cd57a6e5-ce82-3cc5-4bc8-850ddc0c2b94@suse.cz> (raw)
In-Reply-To: <1615891032-29160-2-git-send-email-maninder1.s@samsung.com>
On 3/16/21 11:37 AM, Maninder Singh wrote:
> Adding support for inforamtion of free path along with allocation
> path of an object:
>
> slab kmalloc-64 start c8ab0140 data offset 64 pointer offset 0 size 64 allocated at meminfo_proc_show+0x40/0x4fc
> [ 20.192078] meminfo_proc_show+0x40/0x4fc
> [ 20.192263] seq_read_iter+0x18c/0x4c4
> [ 20.192430] proc_reg_read_iter+0x84/0xac
> [ 20.192617] generic_file_splice_read+0xe8/0x17c
> [ 20.192816] splice_direct_to_actor+0xb8/0x290
> [ 20.193008] do_splice_direct+0xa0/0xe0
> [ 20.193185] do_sendfile+0x2d0/0x438
> [ 20.193345] sys_sendfile64+0x12c/0x140
> [ 20.193523] ret_fast_syscall+0x0/0x58
> [ 20.193695] 0xbeeacde4
> [ 20.193822] Free path:
> [ 20.193935] meminfo_proc_show+0x5c/0x4fc
> [ 20.194115] seq_read_iter+0x18c/0x4c4
> [ 20.194285] proc_reg_read_iter+0x84/0xac
> [ 20.194475] generic_file_splice_read+0xe8/0x17c
> [ 20.194685] splice_direct_to_actor+0xb8/0x290
> [ 20.194870] do_splice_direct+0xa0/0xe0
> [ 20.195014] do_sendfile+0x2d0/0x438
> [ 20.195174] sys_sendfile64+0x12c/0x140
> [ 20.195336] ret_fast_syscall+0x0/0x58
> [ 20.195491] 0xbeeacde4
>
> Co-developed-by: Vaneet Narang <v.narang@samsung.com>
> Signed-off-by: Vaneet Narang <v.narang@samsung.com>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
next prev parent reply other threads:[~2021-03-18 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210316103723epcas5p1f750d5cfe029fa69aea8d88f0bd408f3@epcas5p1.samsung.com>
2021-03-16 10:37 ` [PATCH 1/3] mm/slub: fixing backtrace of objects because of redzone adjustment Maninder Singh
[not found] ` <CGME20210316103736epcas5p3758de57b57c732074acc0989e563cc2e@epcas5p3.samsung.com>
2021-03-16 10:37 ` [PATCH 2/3] mm/slub: Add Support for free path information of an object Maninder Singh
2021-03-18 12:35 ` Vlastimil Babka [this message]
2021-03-19 23:23 ` Paul E. McKenney
[not found] ` <CGME20210316103745epcas5p3994f29958b7f14aec8cbd90fa518761f@epcas5p3.samsung.com>
2021-03-16 10:37 ` [PATCH 3/3] arm: print alloc free paths for address in registers Maninder Singh
2021-03-16 17:44 ` [PATCH 1/3] mm/slub: fixing backtrace of objects because of redzone adjustment Paul E. McKenney
2021-03-18 12:33 ` Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd57a6e5-ce82-3cc5-4bc8-850ddc0c2b94@suse.cz \
--to=vbabka@suse.cz \
--cc=0x7f454c46@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=maninder1.s@samsung.com \
--cc=paulmck@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=v.narang@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).