From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
azurIt <azurit@pobox.sk>,
linux-mm@kvack.org, cgroups@vger.kernel.org, x86@kernel.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 2/6] arch: mm: do not invoke OOM killer on kernel fault OOM
Date: Fri, 26 Jul 2013 15:07:21 +0200 [thread overview]
Message-ID: <20130726130721.GD17761@dhcp22.suse.cz> (raw)
In-Reply-To: <1374791138-15665-3-git-send-email-hannes@cmpxchg.org>
On Thu 25-07-13 18:25:34, Johannes Weiner wrote:
> Kernel faults are expected to handle OOM conditions gracefully (gup,
> uaccess etc.), so they should never invoke the OOM killer. Reserve
> this for faults triggered in user context when it is the only option.
>
> Most architectures already do this, fix up the remaining few.
>
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
I didn't go over all architectures to check whether something slipped
through but the converted ones look OK to me.
Reviewed-by: Michal Hocko <mhocko@suse.cz>
> ---
> arch/arm/mm/fault.c | 14 +++++++-------
> arch/arm64/mm/fault.c | 14 +++++++-------
> arch/avr32/mm/fault.c | 2 +-
> arch/mips/mm/fault.c | 2 ++
> arch/um/kernel/trap.c | 2 ++
> arch/unicore32/mm/fault.c | 14 +++++++-------
> 6 files changed, 26 insertions(+), 22 deletions(-)
>
> diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
> index c97f794..217bcbf 100644
> --- a/arch/arm/mm/fault.c
> +++ b/arch/arm/mm/fault.c
> @@ -349,6 +349,13 @@ retry:
> if (likely(!(fault & (VM_FAULT_ERROR | VM_FAULT_BADMAP | VM_FAULT_BADACCESS))))
> return 0;
>
> + /*
> + * If we are in kernel mode at this point, we
> + * have no context to handle this fault with.
> + */
> + if (!user_mode(regs))
> + goto no_context;
> +
> if (fault & VM_FAULT_OOM) {
> /*
> * We ran out of memory, call the OOM killer, and return to
> @@ -359,13 +366,6 @@ retry:
> return 0;
> }
>
> - /*
> - * If we are in kernel mode at this point, we
> - * have no context to handle this fault with.
> - */
> - if (!user_mode(regs))
> - goto no_context;
> -
> if (fault & VM_FAULT_SIGBUS) {
> /*
> * We had some memory, but were unable to
> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> index 0ecac89..dab1cfd 100644
> --- a/arch/arm64/mm/fault.c
> +++ b/arch/arm64/mm/fault.c
> @@ -294,6 +294,13 @@ retry:
> VM_FAULT_BADACCESS))))
> return 0;
>
> + /*
> + * If we are in kernel mode at this point, we have no context to
> + * handle this fault with.
> + */
> + if (!user_mode(regs))
> + goto no_context;
> +
> if (fault & VM_FAULT_OOM) {
> /*
> * We ran out of memory, call the OOM killer, and return to
> @@ -304,13 +311,6 @@ retry:
> return 0;
> }
>
> - /*
> - * If we are in kernel mode at this point, we have no context to
> - * handle this fault with.
> - */
> - if (!user_mode(regs))
> - goto no_context;
> -
> if (fault & VM_FAULT_SIGBUS) {
> /*
> * We had some memory, but were unable to successfully fix up
> diff --git a/arch/avr32/mm/fault.c b/arch/avr32/mm/fault.c
> index b2f2d2d..2ca27b0 100644
> --- a/arch/avr32/mm/fault.c
> +++ b/arch/avr32/mm/fault.c
> @@ -228,9 +228,9 @@ no_context:
> */
> out_of_memory:
> up_read(&mm->mmap_sem);
> - pagefault_out_of_memory();
> if (!user_mode(regs))
> goto no_context;
> + pagefault_out_of_memory();
> return;
>
> do_sigbus:
> diff --git a/arch/mips/mm/fault.c b/arch/mips/mm/fault.c
> index 85df1cd..94d3a31 100644
> --- a/arch/mips/mm/fault.c
> +++ b/arch/mips/mm/fault.c
> @@ -241,6 +241,8 @@ out_of_memory:
> * (which will retry the fault, or kill us if we got oom-killed).
> */
> up_read(&mm->mmap_sem);
> + if (!user_mode(regs))
> + goto no_context;
> pagefault_out_of_memory();
> return;
>
> diff --git a/arch/um/kernel/trap.c b/arch/um/kernel/trap.c
> index 089f398..b2f5adf 100644
> --- a/arch/um/kernel/trap.c
> +++ b/arch/um/kernel/trap.c
> @@ -124,6 +124,8 @@ out_of_memory:
> * (which will retry the fault, or kill us if we got oom-killed).
> */
> up_read(&mm->mmap_sem);
> + if (!is_user)
> + goto out_nosemaphore;
> pagefault_out_of_memory();
> return 0;
> }
> diff --git a/arch/unicore32/mm/fault.c b/arch/unicore32/mm/fault.c
> index f9b5c10..8ed3c45 100644
> --- a/arch/unicore32/mm/fault.c
> +++ b/arch/unicore32/mm/fault.c
> @@ -278,6 +278,13 @@ retry:
> (VM_FAULT_ERROR | VM_FAULT_BADMAP | VM_FAULT_BADACCESS))))
> return 0;
>
> + /*
> + * If we are in kernel mode at this point, we
> + * have no context to handle this fault with.
> + */
> + if (!user_mode(regs))
> + goto no_context;
> +
> if (fault & VM_FAULT_OOM) {
> /*
> * We ran out of memory, call the OOM killer, and return to
> @@ -288,13 +295,6 @@ retry:
> return 0;
> }
>
> - /*
> - * If we are in kernel mode at this point, we
> - * have no context to handle this fault with.
> - */
> - if (!user_mode(regs))
> - goto no_context;
> -
> if (fault & VM_FAULT_SIGBUS) {
> /*
> * We had some memory, but were unable to
> --
> 1.8.3.2
>
--
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>
next prev parent reply other threads:[~2013-07-26 13:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 22:25 [patch 0/6] improve memcg oom killer robustness Johannes Weiner
2013-07-25 22:25 ` [patch 1/6] arch: mm: remove obsolete init OOM protection Johannes Weiner
2013-07-26 13:00 ` Michal Hocko
2013-07-29 18:55 ` KOSAKI Motohiro
2013-07-25 22:25 ` [patch 2/6] arch: mm: do not invoke OOM killer on kernel fault OOM Johannes Weiner
2013-07-26 13:07 ` Michal Hocko [this message]
2013-07-29 18:58 ` KOSAKI Motohiro
2013-08-01 21:59 ` Johannes Weiner
2013-07-25 22:25 ` [patch 3/6] arch: mm: pass userspace fault flag to generic fault handler Johannes Weiner
2013-07-26 13:19 ` Michal Hocko
2013-07-26 18:45 ` Johannes Weiner
2013-07-25 22:25 ` [patch 4/6] x86: finish user fault error path with fatal signal Johannes Weiner
2013-07-26 13:52 ` Michal Hocko
2013-07-26 18:46 ` Johannes Weiner
2013-07-29 12:45 ` Michal Hocko
2013-07-29 19:01 ` KOSAKI Motohiro
2013-07-25 22:25 ` [patch 5/6] mm: memcg: enable memcg OOM killer only for user faults Johannes Weiner
2013-07-26 14:16 ` Michal Hocko
2013-07-26 18:54 ` Johannes Weiner
2013-07-29 19:18 ` KOSAKI Motohiro
2013-07-29 19:44 ` Johannes Weiner
2013-07-29 19:47 ` KOSAKI Motohiro
2013-07-25 22:25 ` [patch 6/6] mm: memcg: do not trap chargers with full callstack on OOM Johannes Weiner
2013-07-26 14:43 ` Michal Hocko
2013-07-26 21:28 ` Johannes Weiner
2013-07-29 14:12 ` Michal Hocko
2013-07-29 14:55 ` Johannes Weiner
2013-07-29 15:52 ` Michal Hocko
2013-07-30 14:09 ` Michal Hocko
2013-07-30 14:32 ` Johannes Weiner
2013-07-30 14:56 ` Michal Hocko
2013-07-25 22:31 ` [patch 3.2] memcg OOM robustness (x86 only) Johannes Weiner
2013-08-03 8:38 ` azurIt
2013-08-03 16:30 ` Johannes Weiner
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=20130726130721.GD17761@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=azurit@pobox.sk \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).