From: Marco Elver <elver@google.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Kees Cook <keescook@chromium.org>,
Miguel Ojeda <ojeda@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [linux-next:master 9940/10848] thread 'main' panicked at '"ftrace_branch_data_union_(anonymous_at_include/linux/compiler_types_h_174_2)" is not a valid Ident', /opt/cross/rustc-1.68.2-bindgen-0.56.0/cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.24/src/fallback.rs:693:9
Date: Fri, 18 Aug 2023 00:21:00 +0200 [thread overview]
Message-ID: <CANpmjNMFjm0QZqaTwAKdQrBi7qnLv2wAPOXz7frYch-9dUkArA@mail.gmail.com> (raw)
In-Reply-To: <202308171545.aknH9sjQ-lkp@intel.com>
On Thu, 17 Aug 2023 at 09:13, kernel test robot <lkp@intel.com> wrote:
>
> Hi Marco,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 47762f08697484cf0c2f2904b8c52375ed26c8cb
> commit: 7a0fd5e1678505534573b3c14c6ff69ed8592596 [9940/10848] compiler_types: Introduce the Clang __preserve_most function attribute
> config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230817/202308171545.aknH9sjQ-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce: (https://download.01.org/0day-ci/archive/20230817/202308171545.aknH9sjQ-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202308171545.aknH9sjQ-lkp@intel.com/
>
> Note: the linux-next/master HEAD 47762f08697484cf0c2f2904b8c52375ed26c8cb builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> >> thread 'main' panicked at '"ftrace_branch_data_union_(anonymous_at_include/linux/compiler_types_h_174_2)" is not a valid Ident', /opt/cross/rustc-1.68.2-bindgen-0.56.0/cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.24/src/fallback.rs:693:9
> stack backtrace:
> 0: rust_begin_unwind
> at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:575:5
> 1: core::panicking::panic_fmt
> at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:64:14
> 2: proc_macro2::fallback::Ident::_new
> 3: proc_macro2::Ident::new
> 4: bindgen::ir::context::BindgenContext::rust_ident
> 5: <bindgen::ir::comp::CompInfo as bindgen::codegen::CodeGenerator>::codegen
> 6: <bindgen::ir::ty::Type as bindgen::codegen::CodeGenerator>::codegen
> 7: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 8: <bindgen::ir::comp::CompInfo as bindgen::codegen::CodeGenerator>::codegen
> 9: <bindgen::ir::ty::Type as bindgen::codegen::CodeGenerator>::codegen
> 10: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 11: <bindgen::ir::module::Module as bindgen::codegen::CodeGenerator>::codegen
> 12: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 13: bindgen::ir::context::BindgenContext::gen
> 14: bindgen::Builder::generate
> 15: bindgen::main
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
> make[3]: *** [rust/Makefile:316: rust/uapi/uapi_generated.rs] Error 1
> make[3]: *** Deleting file 'rust/uapi/uapi_generated.rs'
> >> thread 'main' panicked at '"ftrace_branch_data_union_(anonymous_at_include/linux/compiler_types_h_174_2)" is
Looks like the commit added some lines before this union, and so the
line numbers have changed. AFAIK this is not a new issue:
https://github.com/Rust-for-Linux/linux/issues/1013
not a valid Ident',
/opt/cross/rustc-1.68.2-bindgen-0.56.0/cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.24/src/fallback.rs:693:9
> stack backtrace:
> 0: rust_begin_unwind
> at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:575:5
> 1: core::panicking::panic_fmt
> at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:64:14
> 2: proc_macro2::fallback::Ident::_new
> 3: proc_macro2::Ident::new
> 4: bindgen::ir::context::BindgenContext::rust_ident
> 5: <bindgen::ir::comp::CompInfo as bindgen::codegen::CodeGenerator>::codegen
> 6: <bindgen::ir::ty::Type as bindgen::codegen::CodeGenerator>::codegen
> 7: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 8: <bindgen::ir::comp::CompInfo as bindgen::codegen::CodeGenerator>::codegen
> 9: <bindgen::ir::ty::Type as bindgen::codegen::CodeGenerator>::codegen
> 10: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 11: <bindgen::ir::module::Module as bindgen::codegen::CodeGenerator>::codegen
> 12: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
> 13: bindgen::ir::context::BindgenContext::gen
> 14: bindgen::Builder::generate
> 15: bindgen::main
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
> make[3]: *** [rust/Makefile:310: rust/bindings/bindings_generated.rs] Error 1
> make[3]: *** Deleting file 'rust/bindings/bindings_generated.rs'
> make[3]: Target 'rust/' not remade because of errors.
> make[2]: *** [Makefile:1281: prepare] Error 2
> make[1]: *** [Makefile:234: __sub-make] Error 2
> make[1]: Target 'prepare' not remade because of errors.
> make: *** [Makefile:234: __sub-make] Error 2
> make: Target 'prepare' not remade because of errors.
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-17 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 7:11 kernel test robot
2023-08-17 22:21 ` Marco Elver [this message]
2023-08-18 7:42 ` Miguel Ojeda
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=CANpmjNMFjm0QZqaTwAKdQrBi7qnLv2wAPOXz7frYch-9dUkArA@mail.gmail.com \
--to=elver@google.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@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