linux-kernel - RE: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 18 Jan 2017 05:13:23 +0000
From:   Matthew Wilcox <mawilcox@...rosoft.com>
To:     kernel test robot <xiaolong.ye@...el.com>,
        Matthew Wilcox <willy@...ux.intel.com>
CC:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Matthew Wilcox <willy@...radead.org>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Konstantin Khlebnikov <koct9i@...il.com>,
        Ross Zwisler <ross.zwisler@...ux.intel.com>,
        Tejun Heo <tj@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>, "lkp@...org" <lkp@...org>
Subject: RE: [lkp-robot] e5a305ac4a:
 WARNING:at_lib/list_debug.c:#__list_del_entry_valid

From: lkp-robot-request@...ists.intel.com [mailto:lkp-robot-request@...ists.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

3. Thank you for reminding me that I need to send Andrew a complete replacement for that patch.