From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: add alignment fault hanling
Date: Tue, 16 Feb 2016 17:11:33 +0000 [thread overview]
Message-ID: <20160216171133.GB24950@localhost.localdomain> (raw)
In-Reply-To: <329817481.954581455597874663.JavaMail.weblogic@epmlwas08c>
On Tue, Feb 16, 2016 at 04:44:38AM +0000, EunTaik Lee wrote:
> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> index 19211c4..a5ebb99 100644
> --- a/arch/arm64/mm/fault.c
> +++ b/arch/arm64/mm/fault.c
> @@ -371,6 +371,14 @@ static int __kprobes do_translation_fault(unsigned long addr,
> return 0;
> }
>
> +static int __kprobes do_alignment_fault(unsigned long addr,
> + unsigned int esr,
> + struct pt_regs *regs)
> +{
> + do_bad_area(addr, esr, regs);
> + return 0;
> +}
> +
> /*
> * This abort handler always returns "fault".
> */
> @@ -418,7 +426,7 @@ static struct fault_info {
> { do_bad, SIGBUS, 0, "synchronous parity error (translation table walk" },
> { do_bad, SIGBUS, 0, "synchronous parity error (translation table walk" },
> { do_bad, SIGBUS, 0, "unknown 32" },
> - { do_bad, SIGBUS, BUS_ADRALN, "alignment fault" },
> + { do_alignment_fault, SIGBUS, BUS_ADRALN, "alignment fault" },
Do you need a new function, can you not just add do_bad_area in the
fault_info array?
--
Catalin
prev parent reply other threads:[~2016-02-16 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 4:44 [PATCH v2] arm64: add alignment fault hanling EunTaik Lee
2016-02-16 10:31 ` Will Deacon
2016-02-16 10:57 ` Robin Murphy
2016-02-16 12:21 ` Catalin Marinas
2016-02-16 16:00 ` Will Deacon
2016-02-16 17:04 ` Will Deacon
2016-02-16 18:50 ` Linus Torvalds
2016-02-16 21:31 ` Arjan van de Ven
2016-02-16 23:04 ` Catalin Marinas
[not found] ` <CA+55aFz+ttJoEG_WkpkwV=+Wunzxpj9NoHobq-8oFZS0HEEyeA@mail.gmail.com>
2016-02-17 0:28 ` Linus Torvalds
2016-02-19 18:14 ` Catalin Marinas
2016-02-19 22:09 ` Linus Torvalds
2016-02-16 17:09 ` Catalin Marinas
2016-02-16 17:11 ` Catalin Marinas [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=20160216171133.GB24950@localhost.localdomain \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).