linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Chen Yucong <slaoub@gmail.com>
Cc: ak@linux.intel.com, Wu Fengguang <fengguang.wu@intel.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH v2] HWPOISON: Fix the handling path of the victimized page frame that belong to non-LUR
Date: Wed,  4 Jun 2014 02:41:01 -0400	[thread overview]
Message-ID: <538ebf9e.4af1e50a.4cd6.231aSMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <1401860898-11486-1-git-send-email-slaoub@gmail.com>

On Wed, Jun 04, 2014 at 01:48:18PM +0800, Chen Yucong wrote:
> Until now, the kernel has the same policy to handle victimized page frames that
> belong to kernel-space(reserved/slab-subsystem) or non-LRU(unknown page state).
> In other word, the result of handling either of these victimized page frames is
> (IGNORED | FAILED), and the return value of memory_failure() is -EBUSY.
> 
> This patch is to avoid that memory_failure() returns very soon due to the "true"
> value of (!PageLRU(p)), and it also ensures that action_result() can report more
> precise information("reserved kernel",  "kernel slab", and "unknown page state")
> instead of "non LRU", especially for memory errors which are detected by memory-scrubbing.
> 
> Changes since v1: http://www.spinics.net/lists/linux-mm/msg74044.html
>   - Call goto just after if (hwpoison_filter(p)) block, and jump directly to just 
>     before the code determining the page_state, as suggested by Naoya Horiguchi.
> 
> Signed-off-by: Chen Yucong <slaoub@gmail.com>

Looks good to me, thanks!

Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>

> ---
>  mm/memory-failure.c |    9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index e3154d9..1340b30 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -862,7 +862,7 @@ static int hwpoison_user_mappings(struct page *p, unsigned long pfn,
>  	struct page *hpage = *hpagep;
>  	struct page *ppage;
>  
> -	if (PageReserved(p) || PageSlab(p))
> +	if (PageReserved(p) || PageSlab(p) || !PageLRU(p))
>  		return SWAP_SUCCESS;
>  
>  	/*
> @@ -1126,9 +1126,6 @@ int memory_failure(unsigned long pfn, int trapno, int flags)
>  					action_result(pfn, "free buddy, 2nd try", DELAYED);
>  				return 0;
>  			}
> -			action_result(pfn, "non LRU", IGNORED);
> -			put_page(p);
> -			return -EBUSY;
>  		}
>  	}
>  
> @@ -1161,6 +1158,9 @@ int memory_failure(unsigned long pfn, int trapno, int flags)
>  		return 0;
>  	}
>  
> +	if (!PageHuge(p) && !PageTransTail(p) && !PageLRU(p))
> +		goto identify_page_state;
> +
>  	/*
>  	 * For error on the tail page, we should set PG_hwpoison
>  	 * on the head page to show that the hugepage is hwpoisoned
> @@ -1210,6 +1210,7 @@ int memory_failure(unsigned long pfn, int trapno, int flags)
>  		goto out;
>  	}
>  
> +identify_page_state:
>  	res = -EBUSY;
>  	/*
>  	 * The first check uses the current page flags which may not have any
> -- 
> 1.7.10.4
> 
> --
> 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>
> 

--
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:[~2014-06-04  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  5:48 Chen Yucong
2014-06-04  6:41 ` Naoya Horiguchi [this message]
     [not found] ` <538ebf9c.c71de50a.0f39.32bdSMTPIN_ADDED_BROKEN@mx.google.com>
2014-06-11  2:11   ` Chen Yucong

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=538ebf9e.4af1e50a.4cd6.231aSMTPIN_ADDED_BROKEN@mx.google.com \
    --to=n-horiguchi@ah.jp.nec.com \
    --cc=ak@linux.intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=slaoub@gmail.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