All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Stevens <stevensd@google.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: Diff in rust/kernel/task.rs:348:
Date: Mon, 31 Aug 2026 02:47:24 +0200	[thread overview]
Message-ID: <202608310257.WibZYb7F-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/David-Stevens/Add-MEMCG-memcg_list_lru_alloc-implementation/20260827-162939
head:   bea0aa5f6ee4e605415210b8979072d03a4c7048
commit: 4535b81f546a9d40371c860407e522d1c088bc8c Set PF_RECLAIMABLE_STACK in various places
date:   3 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260831/202608310257.WibZYb7F-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/20260831/202608310257.WibZYb7F-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/202608310257.WibZYb7F-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 -j128 -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/task.rs:348:
        /// Sets the given task flag bits on the current task.
        #[inline]
        pub fn set_flag_bits(&self, set: u32) {
   -            // SAFETY: The `flags` field of `current` is not modified from other threads, so
   -	    // the non-atomic update isn't a race.
   -	    unsafe { (*self.as_ptr()).flags |= set }
   +        // SAFETY: The `flags` field of `current` is not modified from other threads, so
   +        // the non-atomic update isn't a race.
   +        unsafe { (*self.as_ptr()).flags |= set }
        }
    
        /// Clears the given task flag bits on the current task.
   Diff in rust/kernel/task.rs:357:
        #[inline]
        pub fn clear_flag_bits(&self, clear: u32) {
   -            // SAFETY: The `flags` field of `current` is not modified from other threads, so
   -	    // the non-atomic update isn't a race.
   -	    unsafe { (*self.as_ptr()).flags &= !clear }
   +        // SAFETY: The `flags` field of `current` is not modified from other threads, so
   +        // the non-atomic update isn't a race.
   +        unsafe { (*self.as_ptr()).flags &= !clear }
        }
    }
    
>> Diff in rust/kernel/task.rs:348:
        /// Sets the given task flag bits on the current task.
        #[inline]
        pub fn set_flag_bits(&self, set: u32) {
   -            // SAFETY: The `flags` field of `current` is not modified from other threads, so
   -	    // the non-atomic update isn't a race.
   -	    unsafe { (*self.as_ptr()).flags |= set }
   +        // SAFETY: The `flags` field of `current` is not modified from other threads, so
   +        // the non-atomic update isn't a race.
   +        unsafe { (*self.as_ptr()).flags |= set }
        }
    
        /// Clears the given task flag bits on the current task.
   Diff in rust/kernel/task.rs:357:
        #[inline]
        pub fn clear_flag_bits(&self, clear: u32) {
   -            // SAFETY: The `flags` field of `current` is not modified from other threads, so
   -	    // the non-atomic update isn't a race.
   -	    unsafe { (*self.as_ptr()).flags &= !clear }
   +        // SAFETY: The `flags` field of `current` is not modified from other threads, so
   +        // the non-atomic update isn't a race.
   +        unsafe { (*self.as_ptr()).flags &= !clear }
        }
    }
    
   make[2]: *** [Makefile:1996: rustfmt] Error 123
   make[1]: Leaving directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
   make[2]: Target 'rustfmtcheck' not remade because of errors.
   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-08-31  0:48 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=202608310257.WibZYb7F-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stevensd@google.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 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.