From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Alan Maguire <alan.maguire@oracle.com>, acme@kernel.org
Cc: eddyz87@gmail.com, andrii@kernel.org, mykolal@fb.com,
bpf@vger.kernel.org, dwarves@vger.kernel.org
Subject: Re: [PATCH dwarves v2] btf_encoder: fix memory access bugs
Date: Fri, 31 Jan 2025 14:41:01 -0800 [thread overview]
Message-ID: <c8cf76ab-b00d-42f2-aeb3-143332ea61f5@linux.dev> (raw)
In-Reply-To: <c52fcd63-c85f-41a6-ade4-a42c24c8cef8@oracle.com>
On 1/31/25 5:14 AM, Alan Maguire wrote:
>> [...]
>
> Thanks for the reminder; we'll make sure this one gets applied shortly.
> I wonder if we should add the -fsanitize flags to CFLAGS for RELEASE
mode?
>
The issue with these flags is that they significantly reduce
performance. We might consider adding them for debug builds, but
certainly not for the release.
next prev parent reply other threads:[~2025-01-31 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 18:31 [PATCH dwarves v2] btf_encoder: fix memory access bugs Ihor Solodrai
2025-01-28 0:03 ` ihor.solodrai
2025-01-31 13:14 ` Alan Maguire
2025-01-31 22:41 ` Ihor Solodrai [this message]
2025-03-12 16:52 ` Alan Maguire
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=c8cf76ab-b00d-42f2-aeb3-143332ea61f5@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=mykolal@fb.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