All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: mm/zsmalloc.c:352:2-8: preceding lock on line 347
Date: Mon, 7 Apr 2025 21:05:42 +0800	[thread overview]
Message-ID: <202504072032.LG1Y32Pk-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Sergey Senozhatsky <senozhatsky@chromium.org>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   0af2f6be1b4281385b618cb86ad946eded089ac8
commit: e27af3f9360ee130b7ab0b274088f92146a0855b zsmalloc: sleepable zspage reader-lock
date:   3 weeks ago
:::::: branch date: 17 hours ago
:::::: commit date: 3 weeks ago
config: arm64-randconfig-r061-20250407 (https://download.01.org/0day-ci/archive/20250407/202504072032.LG1Y32Pk-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 92c93f5286b9ff33f27ff694d2dc33da1c07afdd)

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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202504072032.LG1Y32Pk-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> mm/zsmalloc.c:352:2-8: preceding lock on line 347

vim +352 mm/zsmalloc.c

e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  342  
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  343  static __must_check bool zspage_write_trylock(struct zspage *zspage)
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  344  {
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  345  	struct zspage_lock *zsl = &zspage->zsl;
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  346  
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03 @347  	spin_lock(&zsl->lock);
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  348  	if (zsl->cnt == ZS_PAGE_UNLOCKED) {
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  349  		zsl->cnt = ZS_PAGE_WRLOCKED;
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  350  		rwsem_acquire(&zsl->dep_map, 0, 1, _RET_IP_);
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  351  		lock_acquired(&zsl->dep_map, _RET_IP_);
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03 @352  		return true;
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  353  	}
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  354  
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  355  	spin_unlock(&zsl->lock);
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  356  	return false;
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  357  }
e27af3f9360ee13 Sergey Senozhatsky 2025-03-03  358  

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

             reply	other threads:[~2025-04-07 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 13:05 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-21 21:22 mm/zsmalloc.c:352:2-8: preceding lock on line 347 kernel test robot
2026-04-03  8:41 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=202504072032.LG1Y32Pk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=julia.lawall@inria.fr \
    --cc=oe-kbuild@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.