From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Christie <mchristi@redhat.com>
Subject: linux-next: build failure after merge of the ida tree
Date: Fri, 10 Aug 2018 16:36:12 +1000 [thread overview]
Message-ID: <20180810163612.39c88e1e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Hi Matthew,
After merging the ida tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/target/iscsi/iscsi_target_login.c: In function 'iscsi_login_zero_tsih_s1':
drivers/target/iscsi/iscsi_target_login.c:376:16: error: 'sess_idr_lock' undeclared (first use in this function); did you mean 'auth_id_lock'?
spin_lock_bh(&sess_idr_lock);
^~~~~~~~~~~~~
auth_id_lock
drivers/target/iscsi/iscsi_target_login.c:376:16: note: each undeclared identifier is reported only once for each function it appears in
drivers/target/iscsi/iscsi_target_login.c:377:14: error: 'sess_idr' undeclared (first use in this function); did you mean 'sess_ida'?
idr_remove(&sess_idr, sess->session_index);
^~~~~~~~
sess_ida
Caused by commit
9cd88edeaa9d ("target/iscsi: Allocate session IDs from an IDA")
interacting with commit
ad86353cbddb ("iscsi target: fix session creation failure handling")
I have reverted commit 9cd88edeaa9d for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-08-10 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 6:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 6:54 linux-next: build failure after merge of the ida tree Stephen Rothwell
2018-07-18 9:24 ` Pablo Neira Ayuso
2018-07-18 11:59 ` Matthew Wilcox
2018-07-18 13:25 ` Pablo Neira Ayuso
2018-07-18 13:14 ` Matthew Wilcox
2018-07-18 13:27 ` Pablo Neira Ayuso
2018-07-18 13:31 ` Matthew Wilcox
2018-07-18 14:25 ` Pablo Neira Ayuso
2018-07-05 5:13 Stephen Rothwell
2018-07-05 4:36 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=20180810163612.39c88e1e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=willy@infradead.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 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).