From: Jesper Dangaard Brouer <brouer@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Alexander Duyck <alexander.h.duyck@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
brouer@redhat.com
Subject: Re: mm/slub.o:undefined reference to `_GLOBAL_OFFSET_TABLE_'
Date: Thu, 22 Sep 2016 10:29:46 +0200 [thread overview]
Message-ID: <20160922102946.4712077b@redhat.com> (raw)
In-Reply-To: <201609221308.sGPlsAWm%fengguang.wu@intel.com>
On Thu, 22 Sep 2016 13:50:21 +0800
kbuild test robot <fengguang.wu@intel.com> wrote:
> Hi Jesper,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7d1e042314619115153a0f6f06e4552c09a50e13
> commit: d0ecd894e3d5f768a84403b34019c4a7daa05882 slub: optimize bulk slowpath free by detached freelist
> date: 10 months ago
> config: microblaze-allnoconfig (attached as .config)
> compiler: microblaze-linux-gcc (GCC) 6.2.0
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout d0ecd894e3d5f768a84403b34019c4a7daa05882
> # save the attached .config to linux build tree
> make.cross ARCH=microblaze
>
> All errors (new ones prefixed by >>):
>
> mm/built-in.o: In function `__slab_free.isra.14':
> >> mm/slub.o:(.text+0x28d1c): undefined reference to `_GLOBAL_OFFSET_TABLE_'
> scripts/link-vmlinux.sh: line 52: 18051 Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${KBUILD_VMLINUX_INIT} --start-group ${KBUILD_VMLINUX_MAIN} --end-group ${1}
Hi Fengguang,
I don't really understand if this is a real bug that I need to fix?
It looks like a linker problem, resulting in a "Segmentation fault" for your script...
The mentioned commit: d0ecd894e3d5f768a84 removes a call point to
__slab_free() and instead call slab_free(). It does not make sense to
my, why this results in a linker error on this ARCH=microblaze.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Alexander Duyck <alexander.h.duyck@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
brouer@redhat.com
Subject: Re: mm/slub.o:undefined reference to `_GLOBAL_OFFSET_TABLE_'
Date: Thu, 22 Sep 2016 10:29:46 +0200 [thread overview]
Message-ID: <20160922102946.4712077b@redhat.com> (raw)
In-Reply-To: <201609221308.sGPlsAWm%fengguang.wu@intel.com>
On Thu, 22 Sep 2016 13:50:21 +0800
kbuild test robot <fengguang.wu@intel.com> wrote:
> Hi Jesper,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7d1e042314619115153a0f6f06e4552c09a50e13
> commit: d0ecd894e3d5f768a84403b34019c4a7daa05882 slub: optimize bulk slowpath free by detached freelist
> date: 10 months ago
> config: microblaze-allnoconfig (attached as .config)
> compiler: microblaze-linux-gcc (GCC) 6.2.0
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout d0ecd894e3d5f768a84403b34019c4a7daa05882
> # save the attached .config to linux build tree
> make.cross ARCH=microblaze
>
> All errors (new ones prefixed by >>):
>
> mm/built-in.o: In function `__slab_free.isra.14':
> >> mm/slub.o:(.text+0x28d1c): undefined reference to `_GLOBAL_OFFSET_TABLE_'
> scripts/link-vmlinux.sh: line 52: 18051 Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${KBUILD_VMLINUX_INIT} --start-group ${KBUILD_VMLINUX_MAIN} --end-group ${1}
Hi Fengguang,
I don't really understand if this is a real bug that I need to fix?
It looks like a linker problem, resulting in a "Segmentation fault" for your script...
The mentioned commit: d0ecd894e3d5f768a84 removes a call point to
__slab_free() and instead call slab_free(). It does not make sense to
my, why this results in a linker error on this ARCH=microblaze.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2016-09-22 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 5:50 mm/slub.o:undefined reference to `_GLOBAL_OFFSET_TABLE_' kbuild test robot
2016-09-22 8:29 ` Jesper Dangaard Brouer [this message]
2016-09-22 8:29 ` Jesper Dangaard Brouer
2016-09-22 14:43 ` [kbuild-all] " Fengguang Wu
2016-09-22 14:43 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2016-09-16 21:40 kbuild test robot
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=20160922102946.4712077b@redhat.com \
--to=brouer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.