From: patchwork-bot+linux-riscv@kernel.org
To: Matthew Bystrin <dev.mbstr@gmail.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
samuel.holland@sifive.com
Subject: Re: [PATCH v3] riscv: stacktrace: fixed walk_stackframe()
Date: Wed, 22 May 2024 23:51:47 +0000 [thread overview]
Message-ID: <171642190779.9409.5709949427639439601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240521191727.62012-1-dev.mbstr@gmail.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 21 May 2024 22:13:13 +0300 you wrote:
> If the load access fault occures in a leaf function (with
> CONFIG_FRAME_POINTER=y), when wrong stack trace will be displayed:
>
> [<ffffffff804853c2>] regmap_mmio_read32le+0xe/0x1c
> ---[ end trace 0000000000000000 ]---
>
> Registers dump:
> ra 0xffffffff80485758 <regmap_mmio_read+36>
> sp 0xffffffc80200b9a0
> fp 0xffffffc80200b9b0
> pc 0xffffffff804853ba <regmap_mmio_read32le+6>
>
> [...]
Here is the summary with links:
- [v3] riscv: stacktrace: fixed walk_stackframe()
https://git.kernel.org/riscv/c/348212546af0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-05-22 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 19:13 [PATCH v3] riscv: stacktrace: fixed walk_stackframe() Matthew Bystrin
2024-05-21 22:22 ` Samuel Holland
2024-05-22 23:51 ` patchwork-bot+linux-riscv [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=171642190779.9409.5709949427639439601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=dev.mbstr@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=samuel.holland@sifive.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