From: Vineet Gupta <vgupta@kernel.org>
To: Sergey Matyukevich <geomatsi@gmail.com>,
linux-snps-arc@lists.infradead.org
Cc: Vineet Gupta <vgupta@kernel.org>,
Vladimir Isaev <isaev@synopsys.com>,
Sergey Matyukevich <sergey.matyukevich@synopsys.com>
Subject: Re: [PATCH v2 2/4] ARC: entry: fix syscall_trace_exit argument
Date: Mon, 18 Apr 2022 12:14:05 -0700 [thread overview]
Message-ID: <4653468c-f23c-4788-105c-19c6dc9856e2@kernel.org> (raw)
In-Reply-To: <20220414081724.3177956-3-geomatsi@gmail.com>
On 4/14/22 01:17, Sergey Matyukevich wrote:
> From: Sergey Matyukevich<sergey.matyukevich@synopsys.com>
>
> Function syscall_trace_exit expects pointer to pt_regs. However
> r0 is also used to keep syscall return value. Restore pointer
> to pt_regs before calling syscall_trace_exit.
>
> Signed-off-by: Sergey Matyukevich<sergey.matyukevich@synopsys.com>
This is independent fix and worth stable backport, So I'll apply it to
for-curr, rest of the pile goes for next release.
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2022-04-18 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 8:17 [PATCH v2 0/4] ARC: add missing bits for better BPF support Sergey Matyukevich
2022-04-14 8:17 ` [PATCH v2 1/4] ARC: enable HAVE_REGS_AND_STACK_ACCESS_API feature Sergey Matyukevich
2022-04-14 8:17 ` [PATCH v2 2/4] ARC: entry: fix syscall_trace_exit argument Sergey Matyukevich
2022-04-18 19:14 ` Vineet Gupta [this message]
2022-04-14 8:17 ` [PATCH v2 3/4] ARC: implement syscall tracepoints Sergey Matyukevich
2022-04-14 8:17 ` [PATCH v2 4/4] ARC: disasm: handle ARCv2 case in kprobe get/set functions Sergey Matyukevich
2022-04-18 19:10 ` [PATCH v2 0/4] ARC: add missing bits for better BPF support Vineet Gupta
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=4653468c-f23c-4788-105c-19c6dc9856e2@kernel.org \
--to=vgupta@kernel.org \
--cc=geomatsi@gmail.com \
--cc=isaev@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
--cc=sergey.matyukevich@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.