From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: torvalds@linux-foundation.org, mhocko@kernel.org, ben@decadent.org.uk
Cc: akpm@linux-foundation.org, arekm@maven.pl, js1304@gmail.com,
clameter@sgi.com, tj@kernel.org, lkp@01.org,
linux-kernel@vger.kernel.org, mhocko@suse.com
Subject: Re: [PATCH] vmstat: allocate vmstat_wq before it is used
Date: Sat, 9 Jan 2016 15:53:56 +0900 [thread overview]
Message-ID: <201601091553.JJC73408.MLFVFJSOOtQHOF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CA+55aFySZnN0B1rO4iOnFBfAHStzBZS1v8dans1wTn1Uv6Qmtw@mail.gmail.com>
Linus Torvalds wrote:
> On Fri, Jan 8, 2016 at 4:13 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Was there confirmation this fixed the issue? Just verifying..
I confirmed that
----------
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 4ebc17d..0486d3d 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -27,6 +27,7 @@
#include <linux/mm_inline.h>
#include <linux/page_ext.h>
#include <linux/page_owner.h>
+#include <linux/delay.h>
#include "internal.h"
@@ -1550,6 +1551,7 @@ static int __init setup_vmstat(void)
start_shepherd_timer();
cpu_notifier_register_done();
+ ssleep(3);
vmstat_wq = alloc_workqueue("vmstat", WQ_FREEZABLE|WQ_MEM_RECLAIM, 0);
#endif
#ifdef CONFIG_PROC_FS
----------
always reproduces this bug and
----------
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 4ebc17d..358c1b7 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -27,6 +27,7 @@
#include <linux/mm_inline.h>
#include <linux/page_ext.h>
#include <linux/page_owner.h>
+#include <linux/delay.h>
#include "internal.h"
@@ -1483,6 +1484,8 @@ static void __init start_shepherd_timer(void)
BUG();
cpumask_copy(cpu_stat_off, cpu_online_mask);
+ ssleep(3);
+ vmstat_wq = alloc_workqueue("vmstat", WQ_FREEZABLE|WQ_MEM_RECLAIM, 0);
schedule_delayed_work(&shepherd,
round_jiffies_relative(sysctl_stat_interval));
}
@@ -1550,7 +1553,6 @@ static int __init setup_vmstat(void)
start_shepherd_timer();
cpu_notifier_register_done();
- vmstat_wq = alloc_workqueue("vmstat", WQ_FREEZABLE|WQ_MEM_RECLAIM, 0);
#endif
#ifdef CONFIG_PROC_FS
proc_create("buddyinfo", S_IRUGO, NULL, &fragmentation_file_operations);
----------
never reproduces this bug. Thus, I think it is OK to sneak it into 4.4.
>
> Oh, and Tetsuo claims that it needs a cc stable regardless, because
> the commit that caused this to appear was marked for stable and
> already got backported. Yes?
>
> Linus
>
Yes, please.
next prev parent reply other threads:[~2016-01-09 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 2:59 [lkp] [mm, vmstat] 373ccbe592: BUG: unable to handle kernel kernel test robot
2016-01-08 10:18 ` [PATCH] vmstat: allocate vmstat_wq before it is used Michal Hocko
2016-01-09 0:13 ` Linus Torvalds
2016-01-09 0:16 ` Linus Torvalds
2016-01-09 6:53 ` Tetsuo Handa [this message]
2016-01-09 7:07 ` Tetsuo Handa
2016-01-10 20:06 ` Michal Hocko
2016-01-08 10:32 ` [lkp] [mm, vmstat] 373ccbe592: BUG: unable to handle kernel Tetsuo Handa
2016-01-18 2:26 ` Ben Hutchings
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=201601091553.JJC73408.MLFVFJSOOtQHOF@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=ben@decadent.org.uk \
--cc=clameter@sgi.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®