From: Steve French <smfrench@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
CIFS <linux-cifs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Fwd: [EXTERNAL] Re: ioctl.c:undefined reference to `__get_user_bad'
Date: Mon, 17 May 2021 12:13:12 -0500 [thread overview]
Message-ID: <CAH2r5mswqB9DT21YnSXMSAiU0YwFUNu0ni6f=cW+aLz4ssA8rw@mail.gmail.com> (raw)
In-Reply-To: <MN2PR21MB15184963469FEC9B13433964E42D9@MN2PR21MB1518.namprd21.prod.outlook.com>
> 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 >>):
>
> arm-linux-gnueabi-ld: fs/cifs/ioctl.o: in function `cifs_dump_full_key':
>>> ioctl.c:(.text+0x44): undefined reference to `__get_user_bad'
>
<snip>
># CONFIG_MMU is not set
>
>and arch/arm/include/asm/uaccess.h does not implement get_user(size 8 bytes)
> for the non-MMU case:
I see another place in fs/cifs/ioctl.c where we already had been doing
a get_user() into a u64 - any idea what you are supposed to do
instead? Any example code where people have worked around this.
--
Thanks,
Steve
next parent reply other threads:[~2021-05-17 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202105110829.MHq04tJz-lkp@intel.com>
[not found] ` <a022694d-426a-0415-83de-4cc5cd9d1d38@infradead.org>
[not found] ` <MN2PR21MB15184963469FEC9B13433964E42D9@MN2PR21MB1518.namprd21.prod.outlook.com>
2021-05-17 17:13 ` Steve French [this message]
2021-05-17 21:04 ` Fwd: [EXTERNAL] Re: ioctl.c:undefined reference to `__get_user_bad' Randy Dunlap
2021-05-17 21:06 ` Randy Dunlap
2021-05-18 10:03 ` Russell King (Oracle)
2021-05-19 1:48 ` Randy Dunlap
2021-05-19 9:11 ` Aurélien Aptel
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='CAH2r5mswqB9DT21YnSXMSAiU0YwFUNu0ni6f=cW+aLz4ssA8rw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@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).