From: David Marchand <david.marchand@redhat.com>
To: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>,
Sunil Kumar Kori <skori@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] trace: fix out of bounds write in __rte_trace_mem_get
Date: Thu, 3 Apr 2025 11:25:56 +0200 [thread overview]
Message-ID: <CAJFAV8xaLd0wQDFRAFG=oA1MzpDmdLVywCqsabXXQ3nZm7vm=g@mail.gmail.com> (raw)
In-Reply-To: <20250402093309.10394-1-oleksandrn@interfacemasters.com>
On Wed, Apr 2, 2025 at 11:35 AM Oleksandr Nahnybida
<oleksandrn@interfacemasters.com> wrote:
>
> Offset should be aligned first before checking if there is free space for
> another write.
>
> Bugzilla ID: 1665
> Fixes: ebaee6409702 ("trace: simplify trace point headers")
This commit ebaee6409702 ("trace: simplify trace point headers") just
moved code around.
I think the bug was present since the first implementation, so:
Fixes: 032a7e5499a0 ("trace: implement provider payload")
--
David Marchand
prev parent reply other threads:[~2025-04-03 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 9:33 Oleksandr Nahnybida
2025-04-03 9:18 ` [EXTERNAL] " Sunil Kumar Kori
2025-04-03 9:25 ` David Marchand [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='CAJFAV8xaLd0wQDFRAFG=oA1MzpDmdLVywCqsabXXQ3nZm7vm=g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=oleksandrn@interfacemasters.com \
--cc=roretzla@linux.microsoft.com \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
/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 NNTP newsgroup(s).