From: Luis Machado <luis.machado@arm.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH] [opcodes/arm] Fix potential null pointer dereferences
Date: Thu, 10 Nov 2022 01:13:28 +0000 [thread overview]
Message-ID: <bd57bea0-0e14-d2ba-9e3f-83aa73c7a805@arm.com> (raw)
In-Reply-To: <553b4666-0941-746b-d1f2-7ca47a1bb17b@redhat.com>
On 11/3/22 09:14, Nick Clifton wrote:
> Hi Luis,
>
>> PR 29598: dereferenced null pointer in arm-dis.c
>>
>> As pointed out in the bug ticket, we have a couple potential null pointer
>> dereferencing situations for mapping_symbol_for_insn. Harden those.
>
> Approved - please apply.
>
> Cheers
> Nick
>
Thanks. Pushed now.
prev parent reply other threads:[~2022-11-10 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 7:15 Luis Machado
2022-11-03 9:14 ` Nick Clifton
2022-11-10 1:13 ` Luis Machado [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=bd57bea0-0e14-d2ba-9e3f-83aa73c7a805@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).