From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Jan Beulich <jbeulich@suse.com>,
Binutils <binutils@sourceware.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] RISC-V: Fix buffer overflow after long instruction support
Date: Tue, 4 Oct 2022 18:47:32 +0900 [thread overview]
Message-ID: <f5e76b7f-17d4-fd62-5b3c-dcd911d5afa8@irq.a4lg.com> (raw)
In-Reply-To: <ecc23ad1-f856-b01a-e0d5-10aac95cf017@suse.com>
On 2022/10/04 18:44, Jan Beulich wrote:
> On 04.10.2022 11:26, Tsukasa OI wrote:
>> On 2022/10/04 18:07, Jan Beulich wrote:
>>> On 04.10.2022 10:59, Tsukasa OI wrote:
>>>> After commit bb996692bd9 "RISC-V/gas: allow generating up to 176-bit
>>>> instructions with .insn", I started to see some crashes while running
>>>> "make check-gas".
>>>
>>> Hmm, I'm puzzled why things worked correctly for me. The extra size needed
>>> is quite significant, so chances should be rather slim for things to work
>>> correctly.
>>
>> I don't see this extra stack size as a problem so far.
>
> I guess my wording was misleading: I would have expected things for me to
> be broken as well, simply because the amount of overrun would have
> clobbered multiple stack slots (the more that some of my testing was on a
> 32-bit host).
Ah, that would make sense.
Thanks,
Tsukasa
>
> Jan
>
next prev parent reply other threads:[~2022-10-04 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 8:59 Tsukasa OI
2022-10-04 8:59 ` [PATCH 1/2] RISC-V: Fix buffer overflow on print_insn_riscv Tsukasa OI
2022-10-04 8:59 ` [PATCH 2/2] gdb/riscv: Fix buffer overflow on riscv_insn::fetch_instruction Tsukasa OI
2022-10-04 9:04 ` Andreas Schwab
2022-10-04 9:07 ` [PATCH 0/2] RISC-V: Fix buffer overflow after long instruction support Jan Beulich
2022-10-04 9:26 ` Tsukasa OI
2022-10-04 9:44 ` Jan Beulich
2022-10-04 9:47 ` Tsukasa OI [this message]
2022-10-04 9:45 ` [PATCH v2 0/2] RISC-V: Fix buffer overflow after 176-bit " Tsukasa OI
2022-10-04 9:45 ` [PATCH v2 1/2] RISC-V: Fix buffer overflow on print_insn_riscv Tsukasa OI
2022-10-04 9:58 ` Jan Beulich
2022-10-04 10:13 ` Tsukasa OI
2022-10-04 10:16 ` Jan Beulich
2022-10-04 10:18 ` Jan Beulich
2022-10-04 9:45 ` [PATCH v2 2/2] gdb/riscv: Partial support for instructions up to 176-bits Tsukasa OI
2022-10-04 11:25 ` [PATCH v3 0/2] RISC-V: Fix buffer overflow after 176-bit instruction support Tsukasa OI
2022-10-04 11:25 ` [PATCH v3 1/2] RISC-V: Fix buffer overflow on print_insn_riscv Tsukasa OI
2022-10-04 11:25 ` [PATCH v3 2/2] gdb/riscv: Partial support for instructions up to 176-bit Tsukasa OI
2022-10-04 12:23 ` [PATCH v3 0/2] RISC-V: Fix buffer overflow after 176-bit instruction support Jan Beulich
2022-10-04 13:20 ` Nelson Chu
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=f5e76b7f-17d4-fd62-5b3c-dcd911d5afa8@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jbeulich@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).