All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: kbuild test robot <lkp@intel.com>, Michal Simek <monstr@monstr.eu>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leon Romanovsky <leonro@mellanox.com>
Subject: Re: drivers/infiniband/core/.tmp_gl_uverbs_main.o:undefined reference to `__user_bad'
Date: Tue, 1 Jan 2019 20:07:49 +0000	[thread overview]
Message-ID: <20190101200742.GA5757@mellanox.com> (raw)
In-Reply-To: <201901020245.p5MQ8v8e%fengguang.wu@intel.com>

On Wed, Jan 02, 2019 at 02:33:41AM +0800, kbuild test robot wrote:
> Hi Jason,
> 
> FYI, the error/warning still remains.

Like binder, DRM, etc, uverbs requires architectures to support 8 byte
get_user/put_user.

For some reason microblaze only supports 8 byte for put_user, so it
fails to compile.

I don't see a reason to change uverbs here, I think microblaze should
be fixed, then it would fix all the cases below.

Jason

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   e1ef035d272ef4dbfdda98e58699698305138856
> commit: 3a6532c9af1a7836da2d597f1aaca73cb16c3b97 RDMA/uverbs: Use uverbs_attr_bundle to pass udata for write
> date:   5 weeks ago
> config: microblaze-allyesconfig (attached as .config)
> compiler: microblaze-linux-gcc (GCC) 8.1.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 3a6532c9af1a7836da2d597f1aaca73cb16c3b97
>         # save the attached .config to linux build tree
>         GCC_VERSION=8.1.0 make.cross ARCH=microblaze 
> 
> All errors (new ones prefixed by >>):
> 
>    `.exit.data' referenced in section `.exit.text' of drivers/tty/n_hdlc.o: defined in discarded section `.exit.data' of drivers/tty/n_hdlc.o
>    `.exit.data' referenced in section `.exit.text' of drivers/tty/n_hdlc.o: defined in discarded section `.exit.data' of drivers/tty/n_hdlc.o
>    drivers/infiniband/core/uverbs_main.o: In function `ib_uverbs_write':
> >> drivers/infiniband/core/.tmp_gl_uverbs_main.o:(.text+0x13a4): undefined reference to `__user_bad'
>    drivers/android/binder.o: In function `binder_thread_write':
>    drivers/android/.tmp_gl_binder.o:(.text+0xda6c): undefined reference to `__user_bad'
>    drivers/android/.tmp_gl_binder.o:(.text+0xda98): undefined reference to `__user_bad'
>    drivers/android/.tmp_gl_binder.o:(.text+0xdf10): undefined reference to `__user_bad'
>    drivers/android/.tmp_gl_binder.o:(.text+0xe498): undefined reference to `__user_bad'
>    drivers/android/binder.o:drivers/android/.tmp_gl_binder.o:(.text+0xea78): more undefined references to `__user_bad' follow
> 
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation



  reply	other threads:[~2019-01-01 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01 18:33 drivers/infiniband/core/.tmp_gl_uverbs_main.o:undefined reference to `__user_bad' kbuild test robot
2019-01-01 20:07 ` Jason Gunthorpe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-11 14:52 kbuild test robot
     [not found] <201902181136.npHNYgNH%fengguang.wu@intel.com>
2019-02-19  4:00 ` Jason Gunthorpe
2019-02-28  9:03 kbuild test robot
2019-04-03  2:38 ` Randy Dunlap
2019-08-05  4:50   ` Randy Dunlap
2019-08-05  5:03     ` Leon Romanovsky

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=20190101200742.GA5757@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=kbuild-all@01.org \
    --cc=leonro@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=monstr@monstr.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.