From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
"Priya M . A" <priyama2@in.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/book3s64/radix: Avoid WARN_ON in destroy_context
Date: Wed, 25 Sep 2019 21:05:23 +1000 (AEST) [thread overview]
Message-ID: <46dZwM5n2sz9sPJ@ozlabs.org> (raw)
In-Reply-To: <20190918140103.24395-1-aneesh.kumar@linux.ibm.com>
On Wed, 2019-09-18 at 14:01:03 UTC, "Aneesh Kumar K.V" wrote:
> On failed task initialization due to memory allocation failures,
> we can call into destroy_context with process_tb entry set. This patch
> forces the process_tb entry to zero in destroy_context. With
> this patch, we lose the ability to track if we are destroying a context
> without flushing the process table entry.
>
> WARNING: CPU: 4 PID: 6368 at arch/powerpc/mm/mmu_context_book3s64.c:246 destroy_context+0x58/0x340
> NIP [c0000000000875f8] destroy_context+0x58/0x340
> LR [c00000000013da18] __mmdrop+0x78/0x270
> Call Trace:
> [c000000f7db77c80] [c00000000013da18] __mmdrop+0x78/0x270
> [c000000f7db77cf0] [c0000000004d6a34] __do_execve_file.isra.13+0xbd4/0x1000
> [c000000f7db77e00] [c0000000004d7428] sys_execve+0x58/0x70
> [c000000f7db77e30] [c00000000000b388] system_call+0x5c/0x70
>
> Reported-by: Priya M.A <priyama2@in.ibm.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/7aec584eaf1cc1a527dcbe7d80f2e44e3bfcfe1d
cheers
prev parent reply other threads:[~2019-09-25 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 14:01 [PATCH] powerpc/book3s64/radix: Avoid WARN_ON in destroy_context Aneesh Kumar K.V
2019-09-25 11:05 ` Michael Ellerman [this message]
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=46dZwM5n2sz9sPJ@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=priyama2@in.ibm.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;
as well as URLs for NNTP newsgroup(s).