From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'kernel test robot'" <lkp@intel.com>,
"'Hyunchul Lee'" <hyc.lee@gmail.com>
Cc: <kbuild-all@lists.01.org>,
"'Linux Memory Management List'" <linux-mm@kvack.org>,
"'Steve French'" <stfrench@microsoft.com>
Subject: RE: [linux-next:master 1428/6331] fs/cifsd/asn1.c:21:10: fatal error: spnego_negtokeninit.asn1.h: No such file or directory
Date: Fri, 4 Jun 2021 08:29:32 +0900 [thread overview]
Message-ID: <001f01d758d0$4e9e5480$ebdafd80$@samsung.com> (raw)
In-Reply-To: <202106031749.ldQHj6tM-lkp@intel.com>
Hi,
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: ed5d0667a6540293c9485dd95babb5f1e241226a
> commit: fad4161b5cd01a24202234976ebbb133f7adc0b5 [1428/6331] cifsd: decoding gss token using
> lib/asn1_decoder.c
> config: m68k-allmodconfig (attached as .config)
> compiler: m68k-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://protect2.fireeye.com/v1/url?k=57e24f3a-08797620-57e3c475-0cc47a6cba04-
> e1eddf625bb6ef97&q=1&e=d57a7ec3-1031-4dac-b667-
> 8f060adf856a&u=https%3A%2F%2Fraw.githubusercontent.com%2Fintel%2Flkp-
> tests%2Fmaster%2Fsbin%2Fmake.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
> next.git/commit/?id=fad4161b5cd01a24202234976ebbb133f7adc0b5
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout fad4161b5cd01a24202234976ebbb133f7adc0b5
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> fs/cifsd/asn1.c:21:10: fatal error: spnego_negtokeninit.asn1.h: No
> >> such file or directory
> 21 | #include "spnego_negtokeninit.asn1.h"
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
Thanks for report:)
We have already fixed this build error before. And there was the patch for this in linux-next.
"cifsd: fix build break from asn1"
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/fs/cifsd?h=next-20210603&id=5ce071659302aa8d0eed18bfa289c
7dfaf459b63
Thanks!
>
>
> vim +21 fs/cifsd/asn1.c
>
> 17
> 18 #include "asn1.h"
> 19 #include "connection.h"
> 20 #include "auth.h"
> > 21 #include "spnego_negtokeninit.asn1.h"
> 22 #include "spnego_negtokentarg.asn1.h"
> 23
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation https://protect2.fireeye.com/v1/url?k=49363d71-
> 16ad046b-4937b63e-0cc47a6cba04-5a941b2b52fcefa8&q=1&e=d57a7ec3-1031-4dac-b667-
> 8f060adf856a&u=https%3A%2F%2Flists.01.org%2Fhyperkitty%2Flist%2Fkbuild-all%40lists.01.org
prev parent reply other threads:[~2021-06-03 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210603091629epcas1p33e04c74f19fbd8188bc17da7b59bb13f@epcas1p3.samsung.com>
2021-06-03 9:15 ` kernel test robot
2021-06-03 23:29 ` Namjae Jeon [this message]
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='001f01d758d0$4e9e5480$ebdafd80$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyc.lee@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=stfrench@microsoft.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