linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: "Aithal, Srikanth" <sraithal@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: next-20230918: x86 build fails
Date: Tue, 19 Sep 2023 10:47:15 +0200	[thread overview]
Message-ID: <CAP01T74oyzNvNqMq62UvfbkER906skY=wdg9PVMbRQhMOw+1UQ@mail.gmail.com> (raw)
In-Reply-To: <d2b5b60a-7540-5a00-5fca-9690c1db85c4@amd.com>

On Tue, 19 Sept 2023 at 05:55, Aithal, Srikanth <sraithal@amd.com> wrote:
>
> Hi all,
>
> linux-next: next-20230918: x86 build fails with below error:
>
> arch/x86/net/bpf_jit_comp.c: In function ‘arch_bpf_stack_walk’:
> arch/x86/net/bpf_jit_comp.c:3022:72: error: ‘struct unwind_state’ has no
> member named ‘sp’; did you mean ‘bp’?
> 3022 |                 if (!addr || !consume_fn(cookie, (u64)addr,
> (u64)state.sp, (u64)state.bp))
> |                                                                        ^~
> |                                                                        bp
> make[4]: *** [scripts/Makefile.build:243: arch/x86/net/bpf_jit_comp.o]
> Error 1
> make[3]: *** [scripts/Makefile.build:480: arch/x86/net] Error 2
>

Hi,
Thanks for the report. This has been fixed in bpf-next and the fix
should find its way into linux-next soon.
You can locally apply the fix for now to be unstuck.

https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=43c6e890472edf3f667579b0a671f4b3d9b2fa3d

>
>
> Thanks,
> Srikanth Aithal

  reply	other threads:[~2023-09-19  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  3:50 linux-next: Tree for Sep 18 Stephen Rothwell
2023-09-19  3:54 ` linux-next: next-20230918: x86 build fails Aithal, Srikanth
2023-09-19  8:47   ` Kumar Kartikeya Dwivedi [this message]
2023-09-19 13:14     ` Aithal, Srikanth

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='CAP01T74oyzNvNqMq62UvfbkER906skY=wdg9PVMbRQhMOw+1UQ@mail.gmail.com' \
    --to=memxor@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sraithal@amd.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).