All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/rust-kunit-assertion 6/10] Diff in rust/kernel/sync/atomic/predefine.rs:305:
Date: Fri, 02 Oct 2026 05:54:24 +0200	[thread overview]
Message-ID: <202610020520.Xb6jANEo-lkp@intel.com> (raw)

Hi Thomas,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/rust-kunit-assertion
head:   fbe73450cefcca4ff86e4228d44e205327d15c7f
commit: 0c121ebc74a143b8096ec774fcd95f2c438f886e [6/10] prep: atomic
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20261002/202610020520.Xb6jANEo-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261002/202610020520.Xb6jANEo-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/202610020520.Xb6jANEo-lkp@intel.com/

All errors (new ones prefixed by >>):

   PATH=/opt/cross/clang-22/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   INFO PATH=/opt/cross/rustc-1.96.0-bindgen-0.72.1/cargo/bin:/opt/cross/clang-22/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   /usr/bin/timeout -k 100 12h /usr/bin/make KCFLAGS=\ -fno-crash-diagnostics\ -Wno-error=return-type\ -Wreturn-type\ -funsigned-char\ -Wundef\ -falign-functions=64 W=1 --keep-going LLVM=1 -j32 -C source O=/kbuild/obj/consumer/x86_64-rhel-9.4-rust ARCH=x86_64 SHELL=/bin/bash rustfmtcheck 
   make: Entering directory '/kbuild/src'
   make[1]: Entering directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
>> Diff in rust/kernel/sync/atomic/predefine.rs:305:
            let x = Atomic::new(&raw const v);
    
            assert_eq!(x.load(Acquire), &raw const v);
   -        assert_matches!(
   -            x.cmpxchg(&raw const u, &raw const u, Relaxed),
   -            Err(_)
   -        );
   -        assert_matches!(
   -            x.cmpxchg(&raw const v, &raw const u, Relaxed),
   -            Ok(_)
   -        );
   +        assert_matches!(x.cmpxchg(&raw const u, &raw const u, Relaxed), Err(_));
   +        assert_matches!(x.cmpxchg(&raw const v, &raw const u, Relaxed), Ok(_));
            assert_eq!(x.load(Relaxed), &raw const u);
        }
    
>> Diff in rust/kernel/sync/atomic/predefine.rs:305:
            let x = Atomic::new(&raw const v);
    
            assert_eq!(x.load(Acquire), &raw const v);
   -        assert_matches!(
   -            x.cmpxchg(&raw const u, &raw const u, Relaxed),
   -            Err(_)
   -        );
   -        assert_matches!(
   -            x.cmpxchg(&raw const v, &raw const u, Relaxed),
   -            Ok(_)
   -        );
   +        assert_matches!(x.cmpxchg(&raw const u, &raw const u, Relaxed), Err(_));
   +        assert_matches!(x.cmpxchg(&raw const v, &raw const u, Relaxed), Ok(_));
            assert_eq!(x.load(Relaxed), &raw const u);
        }
    
>> Diff in rust/kernel/sync/atomic/predefine.rs:305:
            let x = Atomic::new(&raw const v);
    
            assert_eq!(x.load(Acquire), &raw const v);
   -        assert_matches!(
   -            x.cmpxchg(&raw const u, &raw const u, Relaxed),
   -            Err(_)
   -        );
   -        assert_matches!(
   -            x.cmpxchg(&raw const v, &raw const u, Relaxed),
   -            Ok(_)
   -        );
   +        assert_matches!(x.cmpxchg(&raw const u, &raw const u, Relaxed), Err(_));
   +        assert_matches!(x.cmpxchg(&raw const v, &raw const u, Relaxed), Ok(_));
            assert_eq!(x.load(Relaxed), &raw const u);
        }
    
>> Diff in rust/kernel/sync/atomic/predefine.rs:305:
            let x = Atomic::new(&raw const v);
    
            assert_eq!(x.load(Acquire), &raw const v);
   -        assert_matches!(
   -            x.cmpxchg(&raw const u, &raw const u, Relaxed),
   -            Err(_)
   -        );
   -        assert_matches!(
   -            x.cmpxchg(&raw const v, &raw const u, Relaxed),
   -            Ok(_)
   -        );
   +        assert_matches!(x.cmpxchg(&raw const u, &raw const u, Relaxed), Err(_));
   +        assert_matches!(x.cmpxchg(&raw const v, &raw const u, Relaxed), Ok(_));
            assert_eq!(x.load(Relaxed), &raw const u);
        }
    
   make[2]: *** [Makefile:2038: rustfmt] Error 123
   make[2]: Target 'rustfmtcheck' not remade because of errors.
   make[1]: Leaving directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
   make[1]: *** [Makefile:248: __sub-make] Error 2
   make[1]: Target 'rustfmtcheck' not remade because of errors.
   make: *** [Makefile:248: __sub-make] Error 2
   make: Target 'rustfmtcheck' not remade because of errors.
   make: Leaving directory '/kbuild/src'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-10-02  3:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202610020520.Xb6jANEo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux@weissschuh.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.