From: Jason Low <jason.low2@hpe.com>
To: kbuild test robot <lkp@intel.com>
Cc: jason.low2@hpe.com, kbuild-all@01.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
imre.deak@intel.com, linux-kernel@vger.kernel.org,
Waiman Long <Waiman.Long@hpe.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim Chen <tim.c.chen@linux.intel.com>,
terry.rudd@hpe.com, "Paul E. McKenney" <paulmck@us.ibm.com>,
jason.low2@hp.com
Subject: Re: [PATCH v2] locking/mutex: Prevent lock starvation when spinning is enabled
Date: Tue, 16 Aug 2016 13:19:22 -0700 [thread overview]
Message-ID: <1471378762.29515.4.camel@j-VirtualBox> (raw)
In-Reply-To: <201608110348.S1i8J408%fengguang.wu@intel.com>
On Thu, 2016-08-11 at 04:01 +0800, kbuild test robot wrote:
> Hi Jason,
>
> [auto build test ERROR on tip/locking/core]
> [also build test ERROR on v4.8-rc1 next-20160809]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Jason-Low/locking-mutex-Prevent-lock-starvation-when-spinning-is-enabled/20160811-034327
> config: x86_64-randconfig-x013-201632 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All error/warnings (new ones prefixed by >>):
>
> kernel/locking/mutex.c: In function 'do_yield_to_waiter':
> >> kernel/locking/mutex.c:441:10: error: 'struct mutex' has no member named 'yield_to_waiter'
> if (lock->yield_to_waiter != true)
> ^~
> kernel/locking/mutex.c:442:7: error: 'struct mutex' has no member named 'yield_to_waiter'
> lock->yield_to_waiter = true;
> ^~
> kernel/locking/mutex.c: In function 'clear_yield_to_waiter':
> kernel/locking/mutex.c:447:6: error: 'struct mutex' has no member named 'yield_to_waiter'
> lock->yield_to_waiter = false;
> ^~
> kernel/locking/mutex.c: In function 'need_yield_to_waiter':
> kernel/locking/mutex.c:452:13: error: 'struct mutex' has no member named 'yield_to_waiter'
> return lock->yield_to_waiter;
> ^~
These compilation errors occur in the !SMP case where the
yield_to_waiter variable does not get defined in the mutex structure,
but the waiter yield functions still make use of the variable.
They should be addressed by also checking for #if defined(CONFIG_SMP)
when defining those functions as Waiman had suggested.
Thanks,
Jason
next prev parent reply other threads:[~2016-08-16 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 18:44 [PATCH v2] locking/mutex: Prevent lock starvation when spinning is enabled Jason Low
2016-08-10 20:00 ` kbuild test robot
2016-08-10 20:01 ` kbuild test robot
2016-08-16 20:19 ` Jason Low [this message]
2016-08-10 22:07 ` Jason Low
2016-08-11 2:30 ` Jason Low
2016-08-11 15:40 ` Waiman Long
2016-08-16 19:44 ` Jason Low
2016-08-17 1:41 ` Wanpeng Li
2016-08-17 18:30 ` Jason Low
2016-08-18 0:38 ` Wanpeng Li
2016-08-18 14:14 ` Peter Zijlstra
2016-08-18 15:22 ` Waiman Long
2016-08-18 14:27 ` Peter Zijlstra
2016-08-18 15:18 ` Peter Zijlstra
2016-08-18 15:30 ` Peter Zijlstra
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=1471378762.29515.4.camel@j-VirtualBox \
--to=jason.low2@hpe.com \
--cc=Waiman.Long@hpe.com \
--cc=dave@stgolabs.net \
--cc=imre.deak@intel.com \
--cc=jason.low2@hp.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=paulmck@us.ibm.com \
--cc=peterz@infradead.org \
--cc=terry.rudd@hpe.com \
--cc=tim.c.chen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox