All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	dri-devel@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] kernel/locking: Add context to ww_mutex_trylock.
Date: Tue, 7 Sep 2021 22:59:06 +0800	[thread overview]
Message-ID: <202109072222.zXJ6jimN-lkp@intel.com> (raw)
In-Reply-To: <20210907132044.157225-1-maarten.lankhorst@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 4201 bytes --]

Hi Maarten,

I love your patch! Perhaps something to improve:

[auto build test WARNING on regulator/for-next]
[also build test WARNING on tegra-drm/drm/tegra/for-next v5.14]
[cannot apply to tip/locking/core linus/master next-20210907]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: mips-buildonly-randconfig-r006-20210906 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9c476172b93367d2cb88d7d3f4b1b5b456fa6020)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
        git checkout 1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> kernel/locking/test-ww_mutex.c:138:7: warning: variable 'ret' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:172:9: note: uninitialized use occurs here
           return ret;
                  ^~~
   kernel/locking/test-ww_mutex.c:138:3: note: remove the 'if' if its condition is always false
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:125:9: note: initialize the variable 'ret' to silence this warning
           int ret;
                  ^
                   = 0
   1 warning generated.


vim +138 kernel/locking/test-ww_mutex.c

   120	
   121	static int test_aa(bool trylock)
   122	{
   123		struct ww_mutex mutex;
   124		struct ww_acquire_ctx ctx;
   125		int ret;
   126		const char *from = trylock ? "trylock" : "lock";
   127	
   128		ww_mutex_init(&mutex, &ww_class);
   129		ww_acquire_init(&ctx, &ww_class);
   130	
   131		if (!trylock) {
   132			ret = ww_mutex_lock(&mutex, &ctx);
   133			if (ret) {
   134				pr_err("%s: initial lock failed!\n", __func__);
   135				goto out;
   136			}
   137		} else {
 > 138			if (!ww_mutex_trylock(&mutex, &ctx)) {
   139				pr_err("%s: initial trylock failed!\n", __func__);
   140				goto out;
   141			}
   142		}
   143	
   144		if (ww_mutex_trylock(&mutex, NULL))  {
   145			pr_err("%s: trylocked itself without context from %s!\n", __func__, from);
   146			ww_mutex_unlock(&mutex);
   147			ret = -EINVAL;
   148			goto out;
   149		}
   150	
   151		if (ww_mutex_trylock(&mutex, &ctx))  {
   152			pr_err("%s: trylocked itself with context from %s!\n", __func__, from);
   153			ww_mutex_unlock(&mutex);
   154			ret = -EINVAL;
   155			goto out;
   156		}
   157	
   158		ret = ww_mutex_lock(&mutex, &ctx);
   159		if (ret != -EALREADY) {
   160			pr_err("%s: missed deadlock for recursing, ret=%d from %s\n",
   161			       __func__, ret, from);
   162			if (!ret)
   163				ww_mutex_unlock(&mutex);
   164			ret = -EINVAL;
   165			goto out;
   166		}
   167	
   168		ww_mutex_unlock(&mutex);
   169		ret = 0;
   170	out:
   171		ww_acquire_fini(&ctx);
   172		return ret;
   173	}
   174	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30233 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	dri-devel@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [Intel-gfx] [PATCH] kernel/locking: Add context to ww_mutex_trylock.
Date: Tue, 7 Sep 2021 22:59:06 +0800	[thread overview]
Message-ID: <202109072222.zXJ6jimN-lkp@intel.com> (raw)
In-Reply-To: <20210907132044.157225-1-maarten.lankhorst@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 4201 bytes --]

Hi Maarten,

I love your patch! Perhaps something to improve:

[auto build test WARNING on regulator/for-next]
[also build test WARNING on tegra-drm/drm/tegra/for-next v5.14]
[cannot apply to tip/locking/core linus/master next-20210907]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: mips-buildonly-randconfig-r006-20210906 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9c476172b93367d2cb88d7d3f4b1b5b456fa6020)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
        git checkout 1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> kernel/locking/test-ww_mutex.c:138:7: warning: variable 'ret' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:172:9: note: uninitialized use occurs here
           return ret;
                  ^~~
   kernel/locking/test-ww_mutex.c:138:3: note: remove the 'if' if its condition is always false
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:125:9: note: initialize the variable 'ret' to silence this warning
           int ret;
                  ^
                   = 0
   1 warning generated.


vim +138 kernel/locking/test-ww_mutex.c

   120	
   121	static int test_aa(bool trylock)
   122	{
   123		struct ww_mutex mutex;
   124		struct ww_acquire_ctx ctx;
   125		int ret;
   126		const char *from = trylock ? "trylock" : "lock";
   127	
   128		ww_mutex_init(&mutex, &ww_class);
   129		ww_acquire_init(&ctx, &ww_class);
   130	
   131		if (!trylock) {
   132			ret = ww_mutex_lock(&mutex, &ctx);
   133			if (ret) {
   134				pr_err("%s: initial lock failed!\n", __func__);
   135				goto out;
   136			}
   137		} else {
 > 138			if (!ww_mutex_trylock(&mutex, &ctx)) {
   139				pr_err("%s: initial trylock failed!\n", __func__);
   140				goto out;
   141			}
   142		}
   143	
   144		if (ww_mutex_trylock(&mutex, NULL))  {
   145			pr_err("%s: trylocked itself without context from %s!\n", __func__, from);
   146			ww_mutex_unlock(&mutex);
   147			ret = -EINVAL;
   148			goto out;
   149		}
   150	
   151		if (ww_mutex_trylock(&mutex, &ctx))  {
   152			pr_err("%s: trylocked itself with context from %s!\n", __func__, from);
   153			ww_mutex_unlock(&mutex);
   154			ret = -EINVAL;
   155			goto out;
   156		}
   157	
   158		ret = ww_mutex_lock(&mutex, &ctx);
   159		if (ret != -EALREADY) {
   160			pr_err("%s: missed deadlock for recursing, ret=%d from %s\n",
   161			       __func__, ret, from);
   162			if (!ret)
   163				ww_mutex_unlock(&mutex);
   164			ret = -EINVAL;
   165			goto out;
   166		}
   167	
   168		ww_mutex_unlock(&mutex);
   169		ret = 0;
   170	out:
   171		ww_acquire_fini(&ctx);
   172		return ret;
   173	}
   174	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30233 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] kernel/locking: Add context to ww_mutex_trylock.
Date: Tue, 07 Sep 2021 22:59:06 +0800	[thread overview]
Message-ID: <202109072222.zXJ6jimN-lkp@intel.com> (raw)
In-Reply-To: <20210907132044.157225-1-maarten.lankhorst@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 4312 bytes --]

Hi Maarten,

I love your patch! Perhaps something to improve:

[auto build test WARNING on regulator/for-next]
[also build test WARNING on tegra-drm/drm/tegra/for-next v5.14]
[cannot apply to tip/locking/core linus/master next-20210907]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: mips-buildonly-randconfig-r006-20210906 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9c476172b93367d2cb88d7d3f4b1b5b456fa6020)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install mips cross compiling tool for clang build
        # apt-get install binutils-mips-linux-gnu
        # https://github.com/0day-ci/linux/commit/1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Maarten-Lankhorst/kernel-locking-Add-context-to-ww_mutex_trylock/20210907-212220
        git checkout 1e66afa09b0aa7d6db3122f0312e10d36f6fa217
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> kernel/locking/test-ww_mutex.c:138:7: warning: variable 'ret' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:172:9: note: uninitialized use occurs here
           return ret;
                  ^~~
   kernel/locking/test-ww_mutex.c:138:3: note: remove the 'if' if its condition is always false
                   if (!ww_mutex_trylock(&mutex, &ctx)) {
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/locking/test-ww_mutex.c:125:9: note: initialize the variable 'ret' to silence this warning
           int ret;
                  ^
                   = 0
   1 warning generated.


vim +138 kernel/locking/test-ww_mutex.c

   120	
   121	static int test_aa(bool trylock)
   122	{
   123		struct ww_mutex mutex;
   124		struct ww_acquire_ctx ctx;
   125		int ret;
   126		const char *from = trylock ? "trylock" : "lock";
   127	
   128		ww_mutex_init(&mutex, &ww_class);
   129		ww_acquire_init(&ctx, &ww_class);
   130	
   131		if (!trylock) {
   132			ret = ww_mutex_lock(&mutex, &ctx);
   133			if (ret) {
   134				pr_err("%s: initial lock failed!\n", __func__);
   135				goto out;
   136			}
   137		} else {
 > 138			if (!ww_mutex_trylock(&mutex, &ctx)) {
   139				pr_err("%s: initial trylock failed!\n", __func__);
   140				goto out;
   141			}
   142		}
   143	
   144		if (ww_mutex_trylock(&mutex, NULL))  {
   145			pr_err("%s: trylocked itself without context from %s!\n", __func__, from);
   146			ww_mutex_unlock(&mutex);
   147			ret = -EINVAL;
   148			goto out;
   149		}
   150	
   151		if (ww_mutex_trylock(&mutex, &ctx))  {
   152			pr_err("%s: trylocked itself with context from %s!\n", __func__, from);
   153			ww_mutex_unlock(&mutex);
   154			ret = -EINVAL;
   155			goto out;
   156		}
   157	
   158		ret = ww_mutex_lock(&mutex, &ctx);
   159		if (ret != -EALREADY) {
   160			pr_err("%s: missed deadlock for recursing, ret=%d from %s\n",
   161			       __func__, ret, from);
   162			if (!ret)
   163				ww_mutex_unlock(&mutex);
   164			ret = -EINVAL;
   165			goto out;
   166		}
   167	
   168		ww_mutex_unlock(&mutex);
   169		ret = 0;
   170	out:
   171		ww_acquire_fini(&ctx);
   172		return ret;
   173	}
   174	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30233 bytes --]

  parent reply	other threads:[~2021-09-07 14:59 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 13:20 [PATCH] kernel/locking: Add context to ww_mutex_trylock Maarten Lankhorst
2021-09-07 13:20 ` [Intel-gfx] " Maarten Lankhorst
2021-09-07 13:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-09-07 14:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-07 14:59 ` kernel test robot [this message]
2021-09-07 14:59   ` [PATCH] " kernel test robot
2021-09-07 14:59   ` [Intel-gfx] " kernel test robot
2021-09-07 17:28 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2021-09-08 10:14 ` [PATCH] " Peter Zijlstra
2021-09-08 10:14   ` [Intel-gfx] " Peter Zijlstra
2021-09-08 18:30   ` Daniel Vetter
2021-09-08 18:30     ` [Intel-gfx] " Daniel Vetter
2021-09-09  5:38   ` Maarten Lankhorst
2021-09-09  5:38     ` [Intel-gfx] " Maarten Lankhorst
2021-09-09  8:22     ` Peter Zijlstra
2021-09-09  8:22       ` [Intel-gfx] " Peter Zijlstra
2021-09-09  9:32       ` [PATCH v2] " Maarten Lankhorst
2021-09-09  9:32         ` [Intel-gfx] " Maarten Lankhorst
2021-09-10 15:02         ` Peter Zijlstra
2021-09-10 15:02           ` [Intel-gfx] " Peter Zijlstra
2021-09-10 17:27           ` Peter Zijlstra
2021-09-10 17:27             ` [Intel-gfx] " Peter Zijlstra
2021-09-13  8:42           ` Maarten Lankhorst
2021-09-13  8:42             ` [Intel-gfx] " Maarten Lankhorst
2021-09-14  6:50             ` Peter Zijlstra
2021-09-14  6:50               ` [Intel-gfx] " Peter Zijlstra
2021-09-14 12:43               ` Maarten Lankhorst
2021-09-14 12:43                 ` [Intel-gfx] " Maarten Lankhorst
2021-09-14 13:54                 ` Daniel Vetter
2021-09-14 13:54                   ` [Intel-gfx] " Daniel Vetter
2021-09-16 13:00                   ` Maarten Lankhorst
2021-09-16 13:00                     ` [Intel-gfx] " Maarten Lankhorst
2021-09-16 13:28                     ` Peter Zijlstra
2021-09-16 13:28                       ` [Intel-gfx] " Peter Zijlstra
2021-09-17 13:13                       ` Peter Zijlstra
2021-09-17 13:13                         ` [Intel-gfx] " Peter Zijlstra
2021-09-20 15:02                         ` Joonas Lahtinen
2021-09-20 15:02                           ` [Intel-gfx] " Joonas Lahtinen
2021-09-17 13:17               ` [tip: locking/core] kernel/locking: Add context to ww_mutex_trylock() tip-bot2 for Maarten Lankhorst
2021-11-04 12:27               ` [PATCH] kernel/locking: Use a pointer in ww_mutex_trylock() Sebastian Andrzej Siewior
2021-11-04 12:27                 ` [Intel-gfx] " Sebastian Andrzej Siewior
2021-11-04 12:27                 ` Sebastian Andrzej Siewior
2021-11-17 13:59                 ` [tip: locking/core] " tip-bot2 for Sebastian Andrzej Siewior
2021-09-10 18:06         ` [PATCH v2] kernel/locking: Add context to ww_mutex_trylock Mark Brown
2021-09-10 18:06           ` [Intel-gfx] " Mark Brown
2021-09-09  9:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for kernel/locking: Add context to ww_mutex_trylock. (rev2) Patchwork
2021-09-10 15:36 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for kernel/locking: Add context to ww_mutex_trylock. (rev3) Patchwork
2021-09-14  9:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for kernel/locking: Add context to ww_mutex_trylock. (rev4) Patchwork
2021-09-14  9:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-04 16:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for kernel/locking: Add context to ww_mutex_trylock. (rev5) Patchwork
2021-11-04 18:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-09-09 11:02 [PATCH] kernel/locking: Add context to ww_mutex_trylock kernel test robot
2021-09-14  3:49 ` kernel test robot
2021-09-14  3:49   ` 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=202109072222.zXJ6jimN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=boqun.feng@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lgirdwood@gmail.com \
    --cc=llvm@lists.linux.dev \
    --cc=longman@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@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 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.