From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "kernel test robot" <lkp@intel.com>,
"Danilo Krummrich" <dakr@kernel.org>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>, <rust-for-linux@vger.kernel.org>
Subject: Re: [linux-next:master 3728/9137] samples/rust/rust_driver_auxiliary.o: warning: objtool: _RINvXs5_NtNtCshc5sK6KjdJJ_6kernel5alloc4kboxINtB6_3BoxINtNtNtCsbsbRiabPlh9_4core3mem12maybe_uninit11MaybeUninitINtNtBa_9auxiliary16RegistrationDataNtCseULRbgTYaTO_21rust_driver_auxiliary4DataEENtNtB...
Date: Fri, 29 May 2026 16:54:11 +0900 [thread overview]
Message-ID: <DIUZYLZW1KTM.VRI2RJ8DXEGQ@nvidia.com> (raw)
In-Reply-To: <ahkzosbjO4NdSyD8@google.com>
On Fri May 29, 2026 at 3:35 PM JST, Alice Ryhl wrote:
> On Fri, May 29, 2026 at 10:52:52AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head: f7af91adc230aa99e23330ecf85bc9badd9780ad
>> commit: fd3b87ff0232f46e1ad53a48609a3853c8757c6c [3728/9137] rust: auxiliary: add registration data to auxiliary devices
>> config: x86_64-randconfig-004-20260529 (https://download.01.org/0day-ci/archive/20260529/202605291041.seNEWvLQ-lkp@intel.com/config)
>> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
>> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260529/202605291041.seNEWvLQ-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/202605291041.seNEWvLQ-lkp@intel.com/
>>
>> All warnings (new ones prefixed by >>):
>>
>> samples/rust/rust_driver_auxiliary.o: warning: objtool: asan.module_ctor+0xd: call without frame pointer save/setup
>> samples/rust/rust_driver_auxiliary.o: warning: objtool: asan.module_dtor+0x1: call without frame pointer save/setup
>
> This one looks like this bug:
> https://github.com/rust-lang/rust/pull/156980
Does [1] work around the problem by any chance?
[1] https://lore.kernel.org/all/20260527-nova-exports-v2-3-06de4c556d55@nvidia.com/
next prev parent reply other threads:[~2026-05-29 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202605291041.seNEWvLQ-lkp@intel.com>
2026-05-29 6:35 ` [linux-next:master 3728/9137] samples/rust/rust_driver_auxiliary.o: warning: objtool: _RINvXs5_NtNtCshc5sK6KjdJJ_6kernel5alloc4kboxINtB6_3BoxINtNtNtCsbsbRiabPlh9_4core3mem12maybe_uninit11MaybeUninitINtNtBa_9auxiliary16RegistrationDataNtCseULRbgTYaTO_21rust_driver_auxiliary4DataEENtNtB Alice Ryhl
2026-05-29 7:54 ` Alexandre Courbot [this message]
2026-05-29 8:00 ` Alice Ryhl
2026-05-29 8:19 ` Alexandre Courbot
2026-05-29 9:56 ` Alice Ryhl
2026-05-29 12:13 ` Gary Guo
2026-05-29 13:09 ` Alexandre Courbot
2026-05-29 13:31 ` Gary Guo
2026-05-29 14:00 ` Alexandre Courbot
2026-05-29 14:42 ` Alexandre Courbot
2026-05-29 14:08 ` Alexandre Courbot
2026-05-29 14:24 ` Gary Guo
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=DIUZYLZW1KTM.VRI2RJ8DXEGQ@nvidia.com \
--to=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rust-for-linux@vger.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