From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Corey Minyard <cminyard@mvista.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Subject: linux-next: build failure after merge of the ipmi tree
Date: Wed, 3 Apr 2019 14:33:23 +1100 [thread overview]
Message-ID: <20190403143323.156ac503@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hi Corey,
After merging the ipmi tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/char/ipmi/ipmi_msghandler.c: In function 'free_user':
drivers/char/ipmi/ipmi_msghandler.c:1268:2: error: implicit declaration of function 'cleanup_srcu_struct_quiesced'; did you mean 'cleanup_srcu_struct'? [-Werror=implicit-function-declaration]
cleanup_srcu_struct_quiesced(&user->release_barrier);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
cleanup_srcu_struct
Caused by commit
487ecb21fa66 ("ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier")
interacting with commit
f5ad3991493c ("srcu: Remove cleanup_srcu_struct_quiesced()")
from the rcu tree.
Based on the comments in the rcu tree commit, I have reverted the impi
tree commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-04-03 3:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 3:33 Stephen Rothwell [this message]
2019-04-03 20:27 ` linux-next: build failure after merge of the ipmi tree Corey Minyard
2019-04-03 21:12 ` Corey Minyard
2019-04-04 0:14 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2022-11-04 1:48 Stephen Rothwell
2022-11-04 2:14 ` Corey Minyard
2021-10-01 2:52 Stephen Rothwell
2021-10-01 12:15 ` Corey Minyard
2020-04-20 3:09 Stephen Rothwell
2020-04-20 3:51 ` Feng Tang
2017-09-28 4:45 Stephen Rothwell
2017-09-28 17:34 ` Corey Minyard
2014-12-17 3:03 Stephen Rothwell
2014-12-17 4:22 ` Corey Minyard
2014-11-17 8:20 Stephen Rothwell
2014-11-17 8:14 Stephen Rothwell
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=20190403143323.156ac503@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cminyard@mvista.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).