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  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:   Fri, 1 Mar 2019 21:04:46 +0000
From:   Guillaume Tucker <>
To:     Andrew Morton <>
Cc:     Dan Williams <>,
        Michal Hocko <>,
        Mark Brown <>,
        Tomeu Vizoso <>,
        Matt Hart <>,
        Stephen Rothwell <>,,, Nicholas Piggin <>,
        Dominik Brodowski <>,
        Masahiro Yamada <>,
        Kees Cook <>,
        Adrian Reber <>,
        Linux Kernel Mailing List <>,
        Johannes Weiner <>,
        Linux MM <>,
        Mathieu Desnoyers <>,
        Richard Guy Briggs <>,
        "Peter Zijlstra (Intel)" <>,
Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black

On 01/03/2019 20:41, Andrew Morton wrote:
> On Fri, 1 Mar 2019 09:25:24 +0100 Guillaume Tucker <> wrote:
>>>>> Michal had asked if the free space accounting fix up addressed this
>>>>> boot regression? I was awaiting word on that.
>>>> hm, does actually read emails?  Let's try info@ as well..
>> is not person, it's a send-only account for
>> automated reports.  So no, it doesn't read emails.
>> I guess the tricky point here is that the authors of the commits
>> found by bisections may not always have the hardware needed to
>> reproduce the problem.  So it needs to be dealt with on a
>> case-by-case basis: sometimes they do have the hardware,
>> sometimes someone else on the list or on CC does, and sometimes
>> it's better for the people who have access to the test lab which
>> ran the KernelCI test to deal with it.
>> This case seems to fall into the last category.  As I have access
>> to the Collabora lab, I can do some quick checks to confirm
>> whether the proposed patch does fix the issue.  I hadn't realised
>> that someone was waiting for this to happen, especially as the
>> BeagleBone Black is a very common platform.  Sorry about that,
>> I'll take a look today.
>> It may be a nice feature to be able to give access to the
>> KernelCI test infrastructure to anyone who wants to debug an
>> issue reported by KernelCI or verify a fix, so they won't need to
>> have the hardware locally.  Something to think about for the
>> future.
> Thanks, that all sounds good.
>>>> Is it possible to determine whether this regression is still present in
>>>> current linux-next?
>> I'll try to re-apply the patch that caused the issue, then see if
>> the suggested change fixes it.  As far as the current linux-next
>> master branch is concerned, KernelCI boot tests are passing fine
>> on that platform.
> They would, because I dropped
> mm-shuffle-default-enable-all-shuffling.patch, so your tests presumably
> now have shuffling disabled.
> Is it possible to add the below to linux-next and try again?

I've actually already done that, and essentially the issue can
still be reproduced by applying that patch.  See this branch:

next-20190301 boots fine but the head fails, using
multi_v7_defconfig + SMP=n in both cases and
SHUFFLE_PAGE_ALLOCATOR=y enabled in the 2nd case as a result
of the change in the default value.

The change suggested by Michal Hocko on Feb 15th has now been
applied in linux-next, it's part of this commit but as
explained above it does not actually resolve the boot failure:

  98cf198ee8ce mm: move buddy list manipulations into helpers

I can send more details on Monday and do a bit of debugging to
help narrowing down the problem.  Please let me know if
there's anything in particular that would seem be worth

> Or I can re-add this to linux-next.  Where should we go to determine
> the results of such a change?  There are a heck of a lot of results on
> and entering "beaglebone-black" doesn't get
> me anything.

The BeagleBone Black board was offline for a few days in our
lab, which probably explains why you're not getting much
results from the web interface.  Hopefully we'll see passing
boot results in linux-next tomorrow now that the board is back
on track.

It's quite easy for me to submit test jobs with kernels I've
built myself instead of going through the full linux-next and
KernelCI loop.  So that's the best way to try things out, then
when a fix has been found it can be applied in linux-next on
top of the mm/shuffle change to verify it in KernelCI.


> From: Dan Williams <>
> Subject: mm/shuffle: default enable all shuffling
> Per Andrew's request arrange for all memory allocation shuffling code to
> be enabled by default.
> The page_alloc.shuffle command line parameter can still be used to disable
> shuffling at boot, but the kernel will default enable the shuffling if the
> command line option is not specified.
> Link:
> Signed-off-by: Dan Williams <>
> Cc: Kees Cook <>
> Cc: Michal Hocko <>
> Cc: Dave Hansen <>
> Cc: Keith Busch <>
> Signed-off-by: Andrew Morton <>
> ---
>  init/Kconfig |    4 ++--
>  mm/shuffle.c |    4 ++--
>  mm/shuffle.h |    2 +-
>  3 files changed, 5 insertions(+), 5 deletions(-)
> --- a/init/Kconfig~mm-shuffle-default-enable-all-shuffling
> +++ a/init/Kconfig
> @@ -1709,7 +1709,7 @@ config SLAB_MERGE_DEFAULT
>  	  command line.
> -	default n
> +	default y
>  	depends on SLAB || SLUB
>  	bool "SLAB freelist randomization"
>  	help
> @@ -1728,7 +1728,7 @@ config SLAB_FREELIST_HARDENED
>  	bool "Page allocator randomization"
> +	default y
>  	help
>  	  Randomization of the page allocator improves the average
>  	  utilization of a direct-mapped memory-side-cache. See section
> --- a/mm/shuffle.c~mm-shuffle-default-enable-all-shuffling
> +++ a/mm/shuffle.c
> @@ -9,8 +9,8 @@
>  #include "internal.h"
>  #include "shuffle.h"
> -DEFINE_STATIC_KEY_FALSE(page_alloc_shuffle_key);
> -static unsigned long shuffle_state __ro_after_init;
> +DEFINE_STATIC_KEY_TRUE(page_alloc_shuffle_key);
> +static unsigned long shuffle_state __ro_after_init = 1 << SHUFFLE_ENABLE;
>  /*
>   * Depending on the architecture, module parameter parsing may run
> --- a/mm/shuffle.h~mm-shuffle-default-enable-all-shuffling
> +++ a/mm/shuffle.h
> @@ -19,7 +19,7 @@ enum mm_shuffle_ctl {
> -DECLARE_STATIC_KEY_FALSE(page_alloc_shuffle_key);
> +DECLARE_STATIC_KEY_TRUE(page_alloc_shuffle_key);
>  extern void page_alloc_shuffle(enum mm_shuffle_ctl ctl);
>  extern void __shuffle_free_memory(pg_data_t *pgdat);
>  static inline void shuffle_free_memory(pg_data_t *pgdat)
> _

Powered by blists - more mailing lists