linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Ian Rogers' <irogers@google.com>,
	Numfor Mbiziwo-Tiapo <nums@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>,
	"Namhyung Kim" <namhyung@kernel.org>,
	Song Liu <songliubraving@fb.com>, "mbd@fb.com" <mbd@fb.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>
Subject: RE: [RFC][PATCH 1/2] Fix event.c misaligned address error
Date: Thu, 12 Sep 2019 08:50:57 +0000	[thread overview]
Message-ID: <f8b80a11d1f44503b7dda233a04b11c2@AcuMS.aculab.com> (raw)
In-Reply-To: <CAP-5=fUf1BN634Ojkp-sPUV5iryzZ-qbv_UVS-GoNOgj-454dQ@mail.gmail.com>

From: Ian Rogers
> Sent: 11 September 2019 10:09
> On Wed, Jul 24, 2019 at 3:50 PM Numfor Mbiziwo-Tiapo <nums@google.com> wrote:
> >
> > The ubsan (undefined behavior sanitizer) build of perf throws an
> > error when the synthesize "Synthesize cpu map" function from
> > perf test is run.
> >
> > This can be reproduced by running (from the tip directory):
> > make -C tools/perf USE_CLANG=1 EXTRA_CFLAGS="-fsanitize=undefined"
> >
> > (see cover letter for why perf may not build)
> >
> > then running: tools/perf/perf test 44 -v
> >
> > This bug occurs because the cpu_map_data__synthesize function in
> > event.c calls synthesize_mask, casting the 'data' variable
> > (of type cpu_map_data*) to a cpu_map_mask*. Since struct
> > cpu_map_data is 2 byte aligned and struct cpu_map_mask is 8 byte
> > aligned this causes memory alignment issues.
> >
> > This is fixed by adding 6 bytes of padding to the struct cpu_map_data,
> > however, this will break compatibility between perf data files - a file
> > written by an old perf wouldn't work with a perf with this patch due
> > to event data alignment changing.
> >
> > Comments?
> >
> > Not-Quite-Signed-off-by: Numfor Mbiziwo-Tiapo <nums@google.com>
> > ---
> >  tools/perf/util/event.h | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/tools/perf/util/event.h b/tools/perf/util/event.h
> > index eb95f3384958..82eaf06c2604 100644
> > --- a/tools/perf/util/event.h
> > +++ b/tools/perf/util/event.h
> > @@ -433,6 +433,7 @@ struct cpu_map_mask {
> >
> >  struct cpu_map_data {
> >         u16     type;
> > +       u8 pad[6];
> >         char    data[];
> >  };
> >
> > --
> > 2.22.0.657.g960e92d24f-goog
> >
> An idea here is that, if this breaks backward compatibility, we
> introduce an aligned variant and work to deprecate the unaligned
> variant. I will look into making a patch set.

Adding a pad[6] makes no difference.
You need to add aligened(8) to the structure itself as well.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2019-09-12  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 22:49 [RFC][PATCH 0/2] Perf misaligned address fixes Numfor Mbiziwo-Tiapo
2019-07-24 22:49 ` [RFC][PATCH 1/2] Fix event.c misaligned address error Numfor Mbiziwo-Tiapo
2019-09-11  9:08   ` Ian Rogers
2019-09-12  8:50     ` David Laight [this message]
2019-07-24 22:49 ` [RFC][PATCH 2/2] Fix evsel.c misaligned address errors Numfor Mbiziwo-Tiapo

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=f8b80a11d1f44503b7dda233a04b11c2@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbd@fb.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=nums@google.com \
    --cc=peterz@infradead.org \
    --cc=songliubraving@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;
as well as URLs for NNTP newsgroup(s).