All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: lkp@lists.01.org
Subject: Re: [PATCH] vmstat: allocate vmstat_wq before it is used
Date: Sun, 10 Jan 2016 21:06:58 +0100	[thread overview]
Message-ID: <20160110200657.GA23686@dhcp22.suse.cz> (raw)
In-Reply-To: <CA+55aFySZnN0B1rO4iOnFBfAHStzBZS1v8dans1wTn1Uv6Qmtw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

On Fri 08-01-16 16:16:37, 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..
> 
> 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?

Yes, I have missed that the original patch got backported to 3.2 stable
tree. I do not see it in other branches.

Thanks!
-- 
Michal Hocko
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arkadiusz Miskiewicz <arekm@maven.pl>,
	Joonsoo Kim <js1304@gmail.com>,
	Cristopher Lameter <clameter@sgi.com>, Tejun Heo <tj@kernel.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vmstat: allocate vmstat_wq before it is used
Date: Sun, 10 Jan 2016 21:06:58 +0100	[thread overview]
Message-ID: <20160110200657.GA23686@dhcp22.suse.cz> (raw)
In-Reply-To: <CA+55aFySZnN0B1rO4iOnFBfAHStzBZS1v8dans1wTn1Uv6Qmtw@mail.gmail.com>

On Fri 08-01-16 16:16:37, 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..
> 
> 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?

Yes, I have missed that the original patch got backported to 3.2 stable
tree. I do not see it in other branches.

Thanks!
-- 
Michal Hocko
SUSE Labs

  parent reply	other threads:[~2016-01-10 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  2:59 [mm, vmstat] 373ccbe592: BUG: unable to handle kernel kernel test robot
2016-01-08  2:59 ` [lkp] " kernel test robot
2016-01-08 10:18 ` [PATCH] vmstat: allocate vmstat_wq before it is used Michal Hocko
2016-01-08 10:18   ` Michal Hocko
2016-01-09  0:13   ` Linus Torvalds
2016-01-09  0:13     ` Linus Torvalds
2016-01-09  0:16     ` Linus Torvalds
2016-01-09  0:16       ` Linus Torvalds
2016-01-09  6:53       ` Tetsuo Handa
2016-01-09  6:53         ` Tetsuo Handa
2016-01-09  7:07       ` Tetsuo Handa
2016-01-09  7:07         ` Tetsuo Handa
2016-01-10 20:06       ` Michal Hocko [this message]
2016-01-10 20:06         ` Michal Hocko
2016-01-08 10:32 ` [mm, vmstat] 373ccbe592: BUG: unable to handle kernel Tetsuo Handa
2016-01-08 10:32   ` [lkp] " Tetsuo Handa
2016-01-18  2:26   ` Ben Hutchings
2016-01-18  2:26     ` [lkp] " 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=20160110200657.GA23686@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.