From: Johannes Weiner <hannes@cmpxchg.org>
To: lkp@lists.01.org
Subject: Re: acb32a95a9: BUG: kernel hang in test stage
Date: Wed, 19 Apr 2017 12:46:02 -0400 [thread overview]
Message-ID: <20170419164602.GA4821@cmpxchg.org> (raw)
In-Reply-To: <58f78acc.kZ0tk19VlXn2CBsV%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
Hi,
On Thu, Apr 20, 2017 at 12:05:32AM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.cmpxchg.org/linux-mmotm.git master
>
> commit acb32a95a90a6f88860eb344d04e1634ebbc2170
> Author: mmotm auto import <mm-commits@vger.kernel.org>
> AuthorDate: Thu Apr 13 22:02:16 2017 +0000
> Commit: Johannes Weiner <hannes@cmpxchg.org>
> CommitDate: Thu Apr 13 22:02:16 2017 +0000
>
> linux-next
Hm, you'd think the linux-next commit in the mm tree would produce
problems more often, but this is the first time I've seen it as the
culprit in a problem report.
Do problems usually get spotted inside linux-next.git first and then
the same issues are not reported against the -mm tree?
I also just noticed that <mm-commits@vger.kernel.org> might be a bad
author email since AFAIK it drops everything but akpm-mail. Andrew,
would it be better to set you as the Author of these import patches?
Easy enough to change my scripts.
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: kernel test robot <fengguang.wu@intel.com>
Cc: mmotm auto import <mm-commits@vger.kernel.org>, LKP <lkp@01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
wfg@linux.intel.com
Subject: Re: acb32a95a9: BUG: kernel hang in test stage
Date: Wed, 19 Apr 2017 12:46:02 -0400 [thread overview]
Message-ID: <20170419164602.GA4821@cmpxchg.org> (raw)
In-Reply-To: <58f78acc.kZ0tk19VlXn2CBsV%fengguang.wu@intel.com>
Hi,
On Thu, Apr 20, 2017 at 12:05:32AM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.cmpxchg.org/linux-mmotm.git master
>
> commit acb32a95a90a6f88860eb344d04e1634ebbc2170
> Author: mmotm auto import <mm-commits@vger.kernel.org>
> AuthorDate: Thu Apr 13 22:02:16 2017 +0000
> Commit: Johannes Weiner <hannes@cmpxchg.org>
> CommitDate: Thu Apr 13 22:02:16 2017 +0000
>
> linux-next
Hm, you'd think the linux-next commit in the mm tree would produce
problems more often, but this is the first time I've seen it as the
culprit in a problem report.
Do problems usually get spotted inside linux-next.git first and then
the same issues are not reported against the -mm tree?
I also just noticed that <mm-commits@vger.kernel.org> might be a bad
author email since AFAIK it drops everything but akpm-mail. Andrew,
would it be better to set you as the Author of these import patches?
Easy enough to change my scripts.
--
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 parent reply other threads:[~2017-04-19 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58f78acc.kZ0tk19VlXn2CBsV%fengguang.wu@intel.com>
2017-04-19 16:46 ` Johannes Weiner [this message]
2017-04-19 16:46 ` acb32a95a9: BUG: kernel hang in test stage Johannes Weiner
2017-04-19 17:27 ` Andrew Morton
2017-04-19 17:27 ` Andrew Morton
2017-04-19 17:27 ` Andrew Morton
2017-04-19 17:39 ` Johannes Weiner
2017-04-19 17:39 ` Johannes Weiner
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=20170419164602.GA4821@cmpxchg.org \
--to=hannes@cmpxchg.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.