From: Borislav Petkov <bp@alien8.de>
To: Alexander Potapenko <glider@google.com>,
ZhaoyangHuang <zhaoyang.huang@unisoc.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>, linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"ke.wang" <ke.wang@unisoc.com>,
Matthew Wilcox <willy@infradead.org>,
Zhaoyang Huang <huangzhaoyang@gmail.com>
Subject: Re: Failure during Stack Depot allocating hash table of 1048576 entries with kvcalloc
Date: Sat, 28 Jan 2023 00:16:47 +0100 [thread overview]
Message-ID: <Y9RbX9k/zC6+Eg+u@zn.tnic> (raw)
In-Reply-To: <Y8GCa2CG2Z7hl/5d@zn.tnic>
Ok,
was finally able to bisect it. Lemme add everybody to Cc.
This one reverted ontop of latest Linus master fixes the vmalloc error here:
https://lore.kernel.org/r/Y8Fq5m0CLfcFLCOY@zn.tnic
commit 56a61617dd2276cbc56a6c868599716386d70041 (HEAD, refs/bisect/bad)
Author: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
Date: Thu Oct 27 17:50:24 2022 +0800
mm: use stack_depot for recording kmemleak's backtrace
Using stack_depot to record kmemleak's backtrace which has been
implemented on slub for reducing redundant information.
[akpm@linux-foundation.org: fix build - remove now-unused __save_stack_trace()]
[zhaoyang.huang@unisoc.com: v3]
Link: https://lkml.kernel.org/r/1667101354-4669-1-git-send-email-zhaoyang.huang@unisoc.com
[akpm@linux-foundation.org: fix v3 layout oddities]
[akpm@linux-foundation.org: coding-style cleanups]
Link: https://lkml.kernel.org/r/1666864224-27541-1-git-send-email-zhaoyang.huang@unisoc.com
Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: ke.wang <ke.wang@unisoc.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: Zhaoyang Huang <huangzhaoyang@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-27 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:29 Borislav Petkov
2023-01-13 14:57 ` Alexander Potapenko
2023-01-13 16:10 ` Borislav Petkov
2023-01-27 23:16 ` Borislav Petkov [this message]
2023-01-28 2:41 ` Mirsad Goran Todorovac
2023-01-28 11:03 ` Borislav Petkov
2023-01-28 13:55 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-28 14:26 ` Borislav Petkov
2023-01-29 20:50 ` Andrew Morton
2023-01-29 21:11 ` Borislav Petkov
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=Y9RbX9k/zC6+Eg+u@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=huangzhaoyang@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhaoyang.huang@unisoc.com \
/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