From: "Tobin C. Harding" <me@tobin.cc>
To: kernel test robot <lkp@intel.com>
Cc: "Tobin C. Harding" <tobin@kernel.org>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 15c8410c67 ("mm/slob.c: respect list_head abstraction layer"): WARNING: CPU: 0 PID: 1 at lib/list_debug.c:28 __list_add_valid
Date: Wed, 3 Apr 2019 15:54:17 +1100 [thread overview]
Message-ID: <20190403045417.GA19313@eros.localdomain> (raw)
In-Reply-To: <5ca413c6.9TM84kwWw8lLhnmK%lkp@intel.com>
On Wed, Apr 03, 2019 at 10:00:38AM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit 15c8410c67adefd26ea0df1f1b86e1836051784b
> Author: Tobin C. Harding <tobin@kernel.org>
> AuthorDate: Fri Mar 29 10:01:23 2019 +1100
> Commit: Stephen Rothwell <sfr@canb.auug.org.au>
> CommitDate: Sat Mar 30 16:09:41 2019 +1100
>
> mm/slob.c: respect list_head abstraction layer
>
> Currently we reach inside the list_head. This is a violation of the layer
> of abstraction provided by the list_head. It makes the code fragile.
> More importantly it makes the code wicked hard to understand.
>
> The code logic is based on the page in which an allocation was made, we
> want to modify the slob_list we are working on to have this page at the
> front. We already have a function to check if an entry is at the front of
> the list. Recently a function was added to list.h to do the list
> rotation. We can use these two functions to reduce line count, reduce
> code fragility, and reduce cognitive load required to read the code.
>
> Use list_head functions to interact with lists thereby maintaining the
> abstraction provided by the list_head structure.
>
> Link: http://lkml.kernel.org/r/20190318000234.22049-3-tobin@kernel.org
> Signed-off-by: Tobin C. Harding <tobin@kernel.org>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Cc: Pekka Enberg <penberg@kernel.org>
> Cc: Roman Gushchin <guro@fb.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> 2e1f88301e include/linux/list.h: add list_rotate_to_front()
> 15c8410c67 mm/slob.c: respect list_head abstraction layer
> 05d08e2995 Add linux-next specific files for 20190402
> +-------------------------------------------------------+------------+------------+---------------+
> | | 2e1f88301e | 15c8410c67 | next-20190402 |
> +-------------------------------------------------------+------------+------------+---------------+
> | boot_successes | 1009 | 198 | 299 |
> | boot_failures | 0 | 2 | 44 |
> | WARNING:at_lib/list_debug.c:#__list_add_valid | 0 | 2 | 44 |
> | RIP:__list_add_valid | 0 | 2 | 44 |
> | WARNING:at_lib/list_debug.c:#__list_del_entry_valid | 0 | 2 | 25 |
> | RIP:__list_del_entry_valid | 0 | 2 | 25 |
> | WARNING:possible_circular_locking_dependency_detected | 0 | 2 | 44 |
> | RIP:_raw_spin_unlock_irqrestore | 0 | 2 | 2 |
> | BUG:kernel_hang_in_test_stage | 0 | 0 | 6 |
> | BUG:unable_to_handle_kernel | 0 | 0 | 1 |
> | Oops:#[##] | 0 | 0 | 1 |
> | RIP:slob_page_alloc | 0 | 0 | 1 |
> | Kernel_panic-not_syncing:Fatal_exception | 0 | 0 | 1 |
> | RIP:delay_tsc | 0 | 0 | 2 |
> +-------------------------------------------------------+------------+------------+---------------+
>
> [ 2.618737] db_root: cannot open: /etc/target
> [ 2.620114] mtdoops: mtd device (mtddev=name/number) must be supplied
> [ 2.620967] slram: not enough parameters.
> [ 2.621614] ------------[ cut here ]------------
> [ 2.622254] list_add corruption. prev->next should be next (ffffffffaeeb71b0), but was ffffcee1406d3f70. (prev=ffffcee140422508).
Is this perhaps a false positive because we hackishly move the list_head
'head' and insert it back into the list. Perhaps this is confusing the
validation functions?
Tobin
next prev parent reply other threads:[~2019-04-03 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 2:00 kernel test robot
2019-04-03 4:54 ` Tobin C. Harding [this message]
2019-04-04 4:39 ` Tobin C. Harding
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=20190403045417.GA19313@eros.localdomain \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=tobin@kernel.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