Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Panic in quirk_usb_early_handoff
Date: Sat, 4 Mar 2017 18:29:46 +0100	[thread overview]
Message-ID: <ed4e332d-28d6-e143-b2b3-f1e2829e89a7@free.fr> (raw)
In-Reply-To: <46A35088-88E2-425B-963E-0DC2DCC54890@linaro.org>

On 04/03/2017 18:16, Ard Biesheuvel wrote:

> After pc, the link register is the most likely to legally point into
> the kernel .text section so it makes sense imo to decode the address
> into a function name plus offset.

Does gcc ever use the link register as a general purpose register?
(In which case, it is very likely to contain "garbage" as far as
function addresses are concerned.)

> Educating people about the architecture's calling convention and
> associated caveats is not the job of the panic handler.

That's a weird statement.

Regards.

  reply	other threads:[~2017-03-04 17:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 16:18 Panic in quirk_usb_early_handoff Mason
2017-03-03 17:10 ` Mason
2017-03-03 17:15   ` Mason
2017-03-03 19:02     ` Robin Murphy
2017-03-03 22:09       ` Mason
2017-03-04  0:24       ` Mason
2017-03-04  8:07         ` Ard Biesheuvel
2017-03-04 15:51           ` Alan Stern
2017-03-04 16:57           ` Mason
2017-03-04 17:16             ` Ard Biesheuvel
2017-03-04 17:29               ` Mason [this message]
2017-03-04 18:27                 ` Ard Biesheuvel
2017-03-06 12:42       ` Mason
2017-03-06 13:49         ` Mason
2017-03-06 15:27           ` David Laight
2017-03-06 15:45             ` Mason
2017-03-06 15:58               ` David Laight
2017-03-06 14:30         ` Robin Murphy
2017-03-06 14:56           ` Mason

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=ed4e332d-28d6-e143-b2b3-f1e2829e89a7@free.fr \
    --to=slash.tmp@free.fr \
    --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