linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Marco Elver <elver@google.com>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	"kasan-dev@googlegroups.com" <kasan-dev@googlegroups.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH -next] mm: kence: add __kmem_cache_free to function skip list
Date: Thu, 1 Sep 2022 09:26:54 +0800	[thread overview]
Message-ID: <YxAKXt+a/pqtUmDz@feng-clx> (raw)
In-Reply-To: <7edc9d38-da50-21c8-ea79-f003f386c29b@suse.cz>

On Thu, Sep 01, 2022 at 12:16:17AM +0800, Vlastimil Babka wrote:
> On 8/31/22 16:21, Marco Elver wrote:
> > On Wed, 31 Aug 2022 at 16:04, Hyeonggon Yoo <42.hyeyoo@gmail.com> wrote:
> > 
> >> Maybe you can include those functions too?
> >>
> >> - __kmem_cache_alloc_node
> >> - kmalloc_[node_]trace, kmalloc_large[_node]
> > 
> > This is only required if they are allocator "root" functions when
> > entering allocator code (or may be tail called by a allocator "root"
> > function). Because get_stack_skipnr() looks for one of the listed
> > function prefixes in the whole stack trace.
> > 
> > The reason __kmem_cache_free() is now required is because it is tail
> > called by kfree() which disappears from the stack trace if the
> > compiler does tail-call-optimization.
> 
> I checked and I have this jmp tail call, yet all test pass here.
> But I assume the right commit to amend is
> 05a1c2e50809 ("mm/sl[au]b: generalize kmalloc subsystem")
> 
> Could you Feng maybe verify that that commit is the first that fails the
> tests, and parent commit of that is OK? Thanks.

Yes, 05a1c2e50809 is the first commit that I saw the 4 kfence failed
kunit cases.

Thanks,
Feng



  reply	other threads:[~2022-09-01  1:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  7:30 Feng Tang
2022-08-31  7:35 ` Marco Elver
2022-08-31 11:37   ` Vlastimil Babka
2022-08-31 14:04 ` Hyeonggon Yoo
2022-08-31 14:21   ` Marco Elver
2022-08-31 16:16     ` Vlastimil Babka
2022-09-01  1:26       ` Feng Tang [this message]
2022-09-01  8:47         ` Vlastimil Babka
2022-09-01 12:41           ` Feng Tang
2022-08-31 14:44   ` Feng Tang

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=YxAKXt+a/pqtUmDz@feng-clx \
    --to=feng.tang@intel.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    /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