From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Dmitry Golovin <dima@golovin.in>,
Sedat Dilek <sedat.dilek@gmail.com>
Subject: Re: [PATCH] x86/unwind/orc: Fix ORC unwind table alignment
Date: Wed, 6 Mar 2019 13:04:57 -0600 [thread overview]
Message-ID: <20190306190457.lj46nmqfxvixjnfj@treble> (raw)
In-Reply-To: <CAKwvOdmHe-bkt34E5yf81GoiFRHR8EPnu8wqk2aD2u8P_4Q5jQ@mail.gmail.com>
On Wed, Mar 06, 2019 at 10:44:01AM -0800, Nick Desaulniers wrote:
> On Wed, Mar 6, 2019 at 9:08 AM Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> >
> > The .orc_unwind section is a packed array of 6-byte structs. It's
> > currently aligned to 6 bytes, which is causing warnings in the LLD
> > linker.
> >
> > Six isn't a power of two, so it's not a valid alignment value. The
> > actual alignment doesn't matter much because it's an array of packed
> > structs. An alignment of two is sufficient. In reality it always gets
> > aligned to four bytes because it comes immediately after the
> > 4-byte-aligned .orc_unwind_ip section.
> >
> > Link: https://github.com/ClangBuiltLinux/linux/issues/218
> > Fixes: ee9f8fce9964 ("x86/unwind: Add the ORC unwinder")
>
> Thanks for the patch Josh, we appreciate it. It looks like
> ee9f8fce9964 landed in v4.14-rc1. Should we CC stable?
Yes, that would be a good idea.
Can the tip maintainers please add
Cc: stable@vger.kernel.org
when merging?
--
Josh
next prev parent reply other threads:[~2019-03-06 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:07 Josh Poimboeuf
2019-03-06 18:44 ` Nick Desaulniers
2019-03-06 19:04 ` Josh Poimboeuf [this message]
2019-03-06 19:40 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
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=20190306190457.lj46nmqfxvixjnfj@treble \
--to=jpoimboe@redhat.com \
--cc=dima@golovin.in \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®