From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Matthew Wilcox <mawilcox@microsoft.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Matthew Wilcox <willy@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, "lkp@01.org" <lkp@01.org>
Subject: Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid
Date: Thu, 19 Jan 2017 08:41:23 +0800 [thread overview]
Message-ID: <20170119004123.GB20827@yexl-desktop> (raw)
In-Reply-To: <BY2PR21MB003657B5CEF213783D091C8CCB7F0@BY2PR21MB0036.namprd21.prod.outlook.com>
On 01/18, Matthew Wilcox wrote:
>From: lkp-robot-request@eclists.intel.com [mailto:lkp-robot-request@eclists.intel.com] On Behalf Of kernel test robot
>> FYI, we noticed the following commit:
>>
>> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR
>> and IDA using the radix tree")
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel
>> .org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fnext%2Flinux-
>> next.git&data=02%7C01%7Cmawilcox%40microsoft.com%7C3b615320ff5c48f
>> efde708d43f40a5f9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6
>> 36202994282292096&sdata=vMGk%2FAoZeMkABynnuEIiKM07li%2FzdZlSMM
>> NmwNIGQ1s%3D&reserved=0 master
>
>1. I'm not entirely convinced that this is a reasonable commit to test. Due to the way Andrew has merged a fix for this commit in a second commit, it's expected to be buggy. Although I don't think it could cause this specific failure pattern. Testing commit ffc87d11841ec68a44c57735ff4fada521ab5a27 would make more sense.
>
>2. Ignoring the mangling that outlook has done to that URL, it's pointing somewhere not very useful for a web browser to access: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
>
>Pointing to https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/ would make more sense
Thanks for the suggestion, we'll improve it.
Thanks,
Xiaolong
>
>3. Thank you for reminding me that I need to send Andrew a complete replacement for that patch.
>
next prev parent reply other threads:[~2017-01-19 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:23 [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid kernel test robot
2017-01-18 5:13 ` Matthew Wilcox
2017-01-19 0:41 ` Ye Xiaolong [this message]
2017-01-18 21:09 ` Andrew Morton
2017-01-19 0:40 ` Ye Xiaolong
2017-01-19 0:49 ` Andrew Morton
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=20170119004123.GB20827@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).