mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Jason A. Donenfeld" <zx2c4@kernel.org>
Subject: Re: error[E0080]: evaluation panicked: assertion failed: size_of::<isize>() == size_of::<isize_atomic_repr>()
Date: Mon, 26 Oct 2026 14:55:51 -0700	[thread overview]
Message-ID: <20261026215551.GD1330439@ax162> (raw)
In-Reply-To: <202610261307.vnC1uCAL-lkp@intel.com>

On Mon, Oct 26, 2026 at 01:51:14PM +0100, kernel test robot wrote:
> Hi Nathan,
> 
> FYI, the error/warning still remains.

I think the result of this bisection is wrong. When building at the
parent change (703749b069d5) with this toolchain, there is the error
that this change (eb13a1ff271b) resolves:

  ld.lld: error: undefined symbol: memset
  >>> referenced by getrandom.c:87 (lib/vdso/getrandom.c:87)
  >>>               arch/loongarch/vdso/vgetrandom.o:(__vdso_getrandom)
  make[4]: *** [arch/loongarch/vdso/Makefile:83: arch/loongarch/vdso/vdso.so.dbg] Error 1

If I use LLVM 23.1.4 + rust 1.99.1 to build at the parent change, I can
get the same error reported, so I don't think my change is responsible
for it.

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   6b4b543fa18757297ac756a6fe6e64f506b7844a
> commit: eb13a1ff271b0d180687eebb30611b0b276d5193 random: vDSO: avoid call to memset() when zeroing reserved parameter
> date:   3 weeks ago
> config: loongarch-randconfig-r2103-20261026 (https://download.01.org/0day-ci/archive/20261026/202610261307.vnC1uCAL-lkp@intel.com/config)
> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 42d4451d86c175b745d6ea1c4081787994c7259b)
> rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261026/202610261307.vnC1uCAL-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
> | Fixes: eb13a1ff271b ("random: vDSO: avoid call to memset() when zeroing reserved parameter")
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202610261307.vnC1uCAL-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> error[E0080]: evaluation panicked: assertion failed: size_of::<isize>() == size_of::<isize_atomic_repr>()
>    --> rust/kernel/build_assert.rs:112:23
>    |
>    112 |         const _: () = ::core::assert!($condition $(,$arg)?);
>    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `sync::atomic::predefine::_` failed here
>    |
>    ::: rust/kernel/sync/atomic/predefine.rs:98:1
>    |
>    98 | static_assert!(size_of::<isize>() == size_of::<isize_atomic_repr>());
>    | -------------------------------------------------------------------- in this macro invocation
>    |
>    = note: this error originates in the macro `::core::assert` which comes from the expansion of the macro `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
> --
> >> error[E0080]: evaluation panicked: assertion failed: align_of::<isize>() == align_of::<isize_atomic_repr>()
>    --> rust/kernel/build_assert.rs:112:23
>    |
>    112 |         const _: () = ::core::assert!($condition $(,$arg)?);
>    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `sync::atomic::predefine::_` failed here
>    |
>    ::: rust/kernel/sync/atomic/predefine.rs:99:1
>    |
>    99 | static_assert!(align_of::<isize>() == align_of::<isize_atomic_repr>());
>    | ---------------------------------------------------------------------- in this macro invocation
>    |
>    = note: this error originates in the macro `::core::assert` which comes from the expansion of the macro `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
> --
> >> error[E0080]: evaluation panicked: assertion failed: size_of::<usize>() == size_of::<isize_atomic_repr>()
>    --> rust/kernel/build_assert.rs:112:23
>    |
>    112 |         const _: () = ::core::assert!($condition $(,$arg)?);
>    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `sync::atomic::predefine::_` failed here
>    |
>    ::: rust/kernel/sync/atomic/predefine.rs:100:1
>    |
>    100 | static_assert!(size_of::<usize>() == size_of::<isize_atomic_repr>());
>    | -------------------------------------------------------------------- in this macro invocation
>    |
>    = note: this error originates in the macro `::core::assert` which comes from the expansion of the macro `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
> --
> >> error[E0080]: evaluation panicked: assertion failed: align_of::<usize>() == align_of::<isize_atomic_repr>()
>    --> rust/kernel/build_assert.rs:112:23
>    |
>    112 |         const _: () = ::core::assert!($condition $(,$arg)?);
>    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `sync::atomic::predefine::_` failed here
>    |
>    ::: rust/kernel/sync/atomic/predefine.rs:101:1
>    |
>    101 | static_assert!(align_of::<usize>() == align_of::<isize_atomic_repr>());
>    | ---------------------------------------------------------------------- in this macro invocation
>    |
>    = note: this error originates in the macro `::core::assert` which comes from the expansion of the macro `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
> 
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

-- 
Cheers,
Nathan

  reply	other threads:[~2026-10-26 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 12:51 kernel test robot
2026-10-26 21:55 ` Nathan Chancellor [this message]
2026-10-27  7:24   ` Philip Li
  -- strict thread matches above, loose matches on Subject: below --
2026-10-08 20:01 kernel test robot

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=20261026215551.GD1330439@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zx2c4@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®