linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: subpage_protect: Increase the array size to take care of 64TB
Date: Wed, 06 Aug 2014 16:08:06 +0530	[thread overview]
Message-ID: <87y4v1dhtd.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1405435950-24187-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:

> We now support TASK_SIZE of 16TB, hence the array should be 8.
>
> Fixes the below crash:
>
> Unable to handle kernel paging request for data at address 0x000100bd
> Faulting instruction address: 0xc00000000004f914
> cpu 0x13: Vector: 300 (Data Access) at [c000000fea75fa90]
>     pc: c00000000004f914: .sys_subpage_prot+0x2d4/0x5c0
>     lr: c00000000004fb5c: .sys_subpage_prot+0x51c/0x5c0
>     sp: c000000fea75fd10
>    msr: 9000000000009032
>    dar: 100bd
>  dsisr: 40000000
>   current = 0xc000000fea6ae490
>   paca    = 0xc00000000fb8ab00   softe: 0        irq_happened: 0x00
>     pid   = 8237, comm = a.out
> enter ? for help
> [c000000fea75fe30] c00000000000a164 syscall_exit+0x0/0x98
> --- Exception: c00 (System Call) at 00003fff89737004
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

This should go to stable also. Merged upstream as
dad6f37c2602e4af6c3aecfdb41f2d8bd4668163. Let me know how it should be
handled.

-aneesh

      parent reply	other threads:[~2014-08-06 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 14:52 [PATCH] powerpc: subpage_protect: Increase the array size to take care of 64TB Aneesh Kumar K.V
2014-07-15 15:06 ` Aneesh Kumar K.V
2014-08-06 10:38 ` Aneesh Kumar K.V [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=87y4v1dhtd.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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).