All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0
Date: Fri, 3 Jun 2016 17:46:25 +0100	[thread overview]
Message-ID: <20160603164625.GB2527@techsingularity.net> (raw)
In-Reply-To: <20160603093518.09699af30ba0555847511487@linux-foundation.org>

On Fri, Jun 03, 2016 at 09:35:18AM -0700, Andrew Morton wrote:
> On Fri, 3 Jun 2016 11:00:30 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 
> > In the mean time my tests completed successfully with both patches applied.
> 
> Can we please identify "both patches" with specificity?  I have the
> below one.
> 

mm, page_alloc: Reset zonelist iterator after resetting fair zone allocation policy
mm, page_alloc: Recalculate the preferred zoneref if the context can ignore memory policies

-- 
Mel Gorman
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic: cron/668/0x10c9a0c0
Date: Fri, 3 Jun 2016 17:46:25 +0100	[thread overview]
Message-ID: <20160603164625.GB2527@techsingularity.net> (raw)
In-Reply-To: <20160603093518.09699af30ba0555847511487@linux-foundation.org>

On Fri, Jun 03, 2016 at 09:35:18AM -0700, Andrew Morton wrote:
> On Fri, 3 Jun 2016 11:00:30 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 
> > In the mean time my tests completed successfully with both patches applied.
> 
> Can we please identify "both patches" with specificity?  I have the
> below one.
> 

mm, page_alloc: Reset zonelist iterator after resetting fair zone allocation policy
mm, page_alloc: Recalculate the preferred zoneref if the context can ignore memory policies

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-06-03 16:46 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 13:13 BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice) Geert Uytterhoeven
2016-05-30 13:13 ` Geert Uytterhoeven
2016-05-30 15:56 ` Mel Gorman
2016-05-30 15:56   ` Mel Gorman
2016-05-30 17:37   ` Geert Uytterhoeven
2016-05-30 17:37     ` Geert Uytterhoeven
2016-05-30 17:37     ` Geert Uytterhoeven
2016-05-30 18:56     ` Mel Gorman
2016-05-30 18:56     ` Mel Gorman
2016-05-30 18:56       ` Mel Gorman
2016-05-31  9:28       ` Geert Uytterhoeven
2016-05-31  9:28       ` Geert Uytterhoeven
2016-05-31  9:28         ` Geert Uytterhoeven
2016-05-31 10:13         ` Mel Gorman
2016-05-31 10:13           ` Mel Gorman
2016-05-31 10:13           ` Mel Gorman
2016-05-31 21:44   ` Vlastimil Babka
2016-05-31 21:44   ` Vlastimil Babka
2016-05-31 21:44     ` Vlastimil Babka
2016-06-01  9:19     ` Mel Gorman
2016-06-01  9:19       ` Mel Gorman
2016-06-01 10:01       ` BUG: scheduling while atomic: cron/668/0x10c9a0c0 Vlastimil Babka
2016-06-01 10:01         ` Vlastimil Babka
2016-06-02 10:39         ` Mel Gorman
2016-06-02 10:39           ` Mel Gorman
2016-06-02 12:04           ` Vlastimil Babka
2016-06-02 12:04             ` Vlastimil Babka
2016-06-02 12:04             ` Vlastimil Babka
2016-06-02 12:19             ` Mel Gorman
2016-06-02 12:19               ` Mel Gorman
2016-06-02 12:19               ` Mel Gorman
2016-06-02 18:43               ` Andrew Morton
2016-06-02 18:43                 ` Andrew Morton
2016-06-03  3:52                 ` Stephen Rothwell
2016-06-03  3:52                   ` Stephen Rothwell
2016-06-03  7:57                 ` Geert Uytterhoeven
2016-06-03  7:57                   ` Geert Uytterhoeven
2016-06-03  8:41                   ` Mel Gorman
2016-06-03  8:41                     ` Mel Gorman
2016-06-03  9:00                     ` Geert Uytterhoeven
2016-06-03  9:00                       ` Geert Uytterhoeven
2016-06-03  9:00                       ` Geert Uytterhoeven
2016-06-03 16:35                       ` Andrew Morton
2016-06-03 16:35                         ` Andrew Morton
2016-06-03 16:46                         ` Mel Gorman [this message]
2016-06-03 16:46                           ` Mel Gorman
2016-06-03 16:49                           ` Andrew Morton
2016-06-03 16:49                             ` Andrew Morton
2016-06-02 10:39         ` Mel Gorman
2016-06-01 10:01       ` Vlastimil Babka
2016-06-01  9:19     ` BUG: scheduling while atomic: cron/668/0x10c9a0c0 (was: Re: mm, page_alloc: avoid looking up the first zone in a zonelist twice) Mel Gorman
2016-05-30 15:56 ` Mel Gorman

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=20160603164625.GB2527@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.