From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: linux-next crash during very early boot
Date: Thu, 14 Apr 2016 10:35:47 +0900 [thread overview]
Message-ID: <20160414013546.GA9198@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <3689.1460593786@turing-police.cc.vt.edu>
On Wed, Apr 13, 2016 at 08:29:46PM -0400, Valdis Kletnieks wrote:
> I'm seeing my laptop crash/wedge up/something during very early
> boot - before it can write anything to the console. Nothing in pstore,
> need to hold down the power button for 6 seconds and reboot.
>
> git bisect points at:
>
> commit 7a6bacb133752beacb76775797fd550417e9d3a2
> Author: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Date: Thu Apr 7 13:59:39 2016 +1000
>
> mm/slab: factor out kmem_cache_node initialization code
>
> It can be reused on other place, so factor out it. Following patch will
> use it.
>
>
> Not sure what the problem is - the logic *looks* ok at first read. The
> patch *does* remove a spin_lock_irq() - but I find it difficult to
> believe that with it gone, my laptop is able to hit the race condition
> the spinlock protects against *every single boot*.
>
> The only other thing I see is that n->free_limit used to be assigned
> every time, and now it's only assigned at initial creation.
Hello,
My fault. It should be assgined every time. Please test below patch.
I will send it with proper SOB after you confirm the problem disappear.
Thanks for report and analysis!
Thanks.
---------------->8-----------------
diff --git a/mm/slab.c b/mm/slab.c
index 13e74aa..59dd94a 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -856,8 +856,14 @@ static int init_cache_node(struct kmem_cache *cachep, int node, gfp_t gfp)
* node has not already allocated this
*/
n = get_node(cachep, node);
- if (n)
+ if (n) {
+ spin_lock_irq(&n->list_lock);
+ n->free_limit = (1 + nr_cpus_node(node)) * cachep->batchcount +
+ cachep->num;
+ spin_unlock_irq(&n->list_lock);
+
return 0;
+ }
n = kmalloc_node(sizeof(struct kmem_cache_node), gfp, node);
if (!n)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-04-14 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 0:29 Valdis Kletnieks
2016-04-14 1:35 ` Joonsoo Kim [this message]
2016-04-14 19:22 ` Valdis.Kletnieks
2016-04-15 1:25 ` Joonsoo Kim
2016-04-15 14:10 ` Valdis.Kletnieks
2016-04-20 8:13 ` Joonsoo Kim
2016-04-21 3:14 ` Valdis.Kletnieks
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=20160414013546.GA9198@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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