From: kbuild test robot <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org
Subject: [cifs:for-next 1/1] fs/cifs/smb2transport.c:403:27: error: 'struct cifs_ses' has no member named 'preauth_sha_hash'
Date: Sat, 23 Sep 2017 23:16:48 +0800 [thread overview]
Message-ID: <201709232346.iAmcGGuV%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: a679c0e328c9ba44572af59c90e28fa0b5f1c5a0
commit: a679c0e328c9ba44572af59c90e28fa0b5f1c5a0 [1/1] Fix encryption labels and lengths for SMB3.1.1
config: i386-randconfig-x074-201738 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout a679c0e328c9ba44572af59c90e28fa0b5f1c5a0
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/cifs/smb2transport.c: In function 'generate_smb311signingkey':
>> fs/cifs/smb2transport.c:403:27: error: 'struct cifs_ses' has no member named 'preauth_sha_hash'
d->context.iov_base = ses->preauth_sha_hash;
^~
fs/cifs/smb2transport.c:409:27: error: 'struct cifs_ses' has no member named 'preauth_sha_hash'
d->context.iov_base = ses->preauth_sha_hash;
^~
fs/cifs/smb2transport.c:415:27: error: 'struct cifs_ses' has no member named 'preauth_sha_hash'
d->context.iov_base = ses->preauth_sha_hash;
^~
vim +403 fs/cifs/smb2transport.c
395
396 {
397 struct derivation_triplet triplet;
398 struct derivation *d;
399
400 d = &triplet.signing;
401 d->label.iov_base = "SMBSigningKey";
402 d->label.iov_len = 14;
> 403 d->context.iov_base = ses->preauth_sha_hash;
404 d->context.iov_len = 64;
405
406 d = &triplet.encryption;
407 d->label.iov_base = "SMBC2SCipherKey";
408 d->label.iov_len = 16;
409 d->context.iov_base = ses->preauth_sha_hash;
410 d->context.iov_len = 64;
411
412 d = &triplet.decryption;
413 d->label.iov_base = "SMBS2CCipherKey";
414 d->label.iov_len = 16;
415 d->context.iov_base = ses->preauth_sha_hash;
416 d->context.iov_len = 64;
417
418 return generate_smb3signingkey(ses, &triplet);
419 }
420
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30824 bytes --]
reply other threads:[~2017-09-23 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201709232346.iAmcGGuV%fengguang.wu@intel.com \
--to=fengguang.wu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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