On Tue, Oct 25, 2022 at 9:53 AM Nathan Chancellor <nathan@xxxxxxxxxx> wrote:
>
> On Mon, Oct 24, 2022 at 02:06:52PM -0700, Nick Desaulniers wrote:
> > Dear stable kernel maintainers,
> > Our production kernel team and ChromeOS kernel teams are reporting
> > that they are unable to symbolize addresses of symbols defined in
> > assembly sources due to a regression I caused with
> > commit a66049e2cf0e ("Kbuild: make DWARF version a choice")
>
> I think you mean commit b8a9092330da ("Kbuild: do not emit debug info
> for assembly with LLVM_IAS=1"), which is what you blamed in
> 32ef9e5054ec? a66049e2cf0e does not appear to have any affect on this
> problem?
Ah right, grabbed the wrong sha from the commit messages.
Not an issue in the patches, just the initial email I sent. Should
still be good for stable maintainers to pick up.
>
> > I fixed this upstream with
> > commit 32ef9e5054ec ("Makefile.debug: re-enable debug info for .S files")
> > but I think this is infeasible to backport through to 4.19.y.
> >
> > Do the attached branch-specific variants look acceptable?
>
> I think the stable specific versions should be okay. We should be able
> to deal with any fallout that happens if there is any.
>
> Acked-by: Nathan Chancellor <nathan@xxxxxxxxxx>
Thanks for triple checking!
--
Thanks,
~Nick Desaulniers
