linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: rientjes@google.com, hannes@cmpxchg.org, linux-mm@kvack.org
Subject: Re: [REPOST] [PATCH 2/2] mm: Fix potentially scheduling in GFP_ATOMIC allocations.
Date: Mon, 24 Aug 2015 10:54:19 +0200	[thread overview]
Message-ID: <20150824085419.GD17078@dhcp22.suse.cz> (raw)
In-Reply-To: <201508231623.DED13020.tFOHFVFQOSOLMJ@I-love.SAKURA.ne.jp>

On Sun 23-08-15 16:23:37, Tetsuo Handa wrote:
> >From 08a638e04351386ab03cd1223988ac7940d4d3aa Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Sat, 1 Aug 2015 22:46:12 +0900
> Subject: [PATCH 2/2] mm: Fix potentially scheduling in GFP_ATOMIC
>  allocations.
> 
> Currently, if somebody does GFP_ATOMIC | __GFP_NOFAIL allocation,

This combination of flags is broken by definition and I fail to see it
being used anywhere in the kernel.

> wait_iff_congested() might be called via __alloc_pages_high_priority()
> before reaching
> 
>   if (!wait) {
>     WARN_ON_ONCE(gfp_mask & __GFP_NOFAIL);
>     goto nopage;
>   }

> 
> because gfp_to_alloc_flags() includes ALLOC_NO_WATERMARKS if TIF_MEMDIE
> was set.
> 
> We need to check for __GFP_WAIT flag at __alloc_pages_high_priority()
> in order to make sure that we won't schedule.

I do not think this is an improvement. It is true we are already failing
__GFP_NOFAIL & ~__GFP_WAIT but I believe it doesn't make much sense
to replace one buggy behavior (sleeping in atomic context) by another
(failing __GFP_NOFAIL). It is the caller which should be fixed here. We
should get "scheduling while atomic:" and the trace with the current
code so we are not loosing any debugging options.

> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
>  mm/page_alloc.c | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 37a0390..f9f09fa 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2917,16 +2917,15 @@ __alloc_pages_high_priority(gfp_t gfp_mask, unsigned int order,
>  {
>  	struct page *page;
>  
> -	do {
> +	for (;;) {
>  		page = get_page_from_freelist(gfp_mask, order,
>  						ALLOC_NO_WATERMARKS, ac);
>  
> -		if (!page && gfp_mask & __GFP_NOFAIL)
> -			wait_iff_congested(ac->preferred_zone, BLK_RW_ASYNC,
> -									HZ/50);
> -	} while (!page && (gfp_mask & __GFP_NOFAIL));
> -
> -	return page;
> +		if (page || (gfp_mask & (__GFP_NOFAIL | __GFP_WAIT)) !=
> +		    (__GFP_NOFAIL | __GFP_WAIT))
> +			return page;
> +		wait_iff_congested(ac->preferred_zone, BLK_RW_ASYNC, HZ/50);
> +	}
>  }
>  
>  static void wake_all_kswapds(unsigned int order, const struct alloc_context *ac)
> -- 
> 1.8.3.1

-- 
Michal Hocko
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:[~2015-08-24  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23  7:23 Tetsuo Handa
2015-08-24  8:54 ` Michal Hocko [this message]
2015-09-01 22:21 ` David Rientjes
2015-09-03  8:55   ` Tetsuo Handa
2015-09-09 22:23     ` David Rientjes

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=20150824085419.GD17078@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rientjes@google.com \
    /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