From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Avoid unaligned pointer operations
Date: Thu, 12 Dec 2024 17:46:00 -0800 [thread overview]
Message-ID: <Z1uR2EhgfuzLL3a4@google.com> (raw)
In-Reply-To: <CAP-5=fW5bbxXakiFuUAG-HTH2aH_hTXQjJp6o-bZcjcPvNmVrA@mail.gmail.com>
On Thu, Dec 12, 2024 at 03:56:31PM -0800, Ian Rogers wrote:
> On Wed, Nov 27, 2024 at 1:26 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > The sample data is 64-bit aligned basically but raw data starts with
> > 32-bit length field and data follows. In perf_event__synthesize_sample
> > it treats the sample data as a 64-bit array. And it needs some trick
> > to update the raw data properly.
> >
> > But it seems some compilers are not happy with this and the program dies
> > siliently. I found the sample parsing test failed without any messages
> > on affected systems.
> >
> > Let's update the code to use a 32-bit pointer directly and make sure the
> > result is 64-bit aligned again. No functional changes intended.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/util/synthetic-events.c | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
> >
> > diff --git a/tools/perf/util/synthetic-events.c b/tools/perf/util/synthetic-events.c
> > index a58444c4aed1f1ea..385383ef6cf1edaf 100644
> > --- a/tools/perf/util/synthetic-events.c
> > +++ b/tools/perf/util/synthetic-events.c
> > @@ -1686,12 +1686,16 @@ int perf_event__synthesize_sample(union perf_event *event, u64 type, u64 read_fo
> > }
> >
> > if (type & PERF_SAMPLE_RAW) {
> > - u.val32[0] = sample->raw_size;
> > - *array = u.val64;
> > - array = (void *)array + sizeof(u32);
> > + u32 *array32 = (void *)array;
> > +
> > + *array32 = sample->raw_size;
> > + array32++;
> > +
> > + memcpy(array32, sample->raw_data, sample->raw_size);
> > + array = (void *)(array32 + (sample->raw_size / sizeof(u32)));
> >
> > - memcpy(array, sample->raw_data, sample->raw_size);
> > - array = (void *)array + sample->raw_size;
> > + /* make sure the array is 64-bit aligned */
> > + BUG_ON(((long)array) / sizeof(u64));
>
> I think you intended:
>
> BUG_ON(((long)array) % sizeof(u64));
Yep, fixed in v2.
https://lore.kernel.org/r/20241128010325.946897-1-namhyung@kernel.org
Thanks,
Namhyung
prev parent reply other threads:[~2024-12-13 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 21:26 [PATCH] perf tools: Avoid unaligned pointer operations Namhyung Kim
2024-11-28 0:51 ` Ian Rogers
2024-12-12 18:41 ` Arnaldo Carvalho de Melo
2024-12-12 21:00 ` Namhyung Kim
2024-12-12 22:20 ` Ian Rogers
2024-12-12 23:56 ` Ian Rogers
2024-12-13 1:46 ` Namhyung Kim [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=Z1uR2EhgfuzLL3a4@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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