linux-kernel - Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice)

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]

Message-ID: <CAMuHMdWioTRo1PGymqCEv+3CoQYH8qnhP2T__orSbMw1q-CBMA@mail.gmail.com>
Date:	Mon, 30 May 2016 19:37:39 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Mel Gorman <mgorman@...hsingularity.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux MM <linux-mm@...ck.org>,
	linux-m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm,
 page_alloc: avoid looking up the first zone in a zonelist twice)

Hi Mel,

On Mon, May 30, 2016 at 5:56 PM, Mel Gorman <mgorman@...hsingularity.net> wrote:
> On Mon, May 30, 2016 at 03:13:40PM +0200, Geert Uytterhoeven wrote:
>> >     The benefit is negligible and the results are within the noise but each
>> >     cycle counts.
>> >
>> >     Signed-off-by: Mel Gorman <mgorman@...hsingularity.net>
>> >     Cc: Vlastimil Babka <vbabka@...e.cz>
>> >     Cc: Jesper Dangaard Brouer <brouer@...hat.com>
>> >     Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
>> >     Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
>>
>> About one week ago, I started seeing an obscure intermittent crash during
>> system shutdown on m68k/ARAnyM using atari_defconfig.
>> The crash isn't 100% reproducible, but it happens during ca. 1 out of 5
>> shutdowns.
>>
>> I finally managed to bisect it to the above commit.
>> I did verify that the parent commit didn't crash after 60 tries.
>> Unfortunately I couldn't revert the offending commit on top of v4.7-rc1, due to
>> conflicting changes.
>>
>> Do you have any idea what's going wrong?
>
> There isn't anything obvious from the crash log you showed but can you
> try the following just in case?
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index dba8cfd0b2d6..f2c1e47adc11 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -3232,6 +3232,9 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
>                  * allocations are system rather than user orientated
>                  */
>                 ac->zonelist = node_zonelist(numa_node_id(), gfp_mask);
> +               ac->preferred_zoneref = first_zones_zonelist(ac->zonelist,
> +                                       ac->high_zoneidx, ac->nodemask);
> +               ac->classzone_idx = zonelist_zone_idx(ac->preferred_zoneref);
>                 page = get_page_from_freelist(gfp_mask, order,
>                                                 ALLOC_NO_WATERMARKS, ac);
>                 if (page)

Thanks, but unfortunately it doesn't help.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds