On 12/18/2016, 03:54 PM, Nikolay Borisov wrote:
>
>
> On 18.12.2016 16:45, Jiri Slaby wrote:
>> Moreover, with some modules, __put_user_1 and others are reported
>> instead of mcount.
>
>
> nm vmlinux | grep __fentry__
> nm vmlinux | grep mcount
>
> What do these report ? I bet you that in
On 12/18/2016, 03:54 PM, Nikolay Borisov wrote:
>
>
> On 18.12.2016 16:45, Jiri Slaby wrote:
>> Moreover, with some modules, __put_user_1 and others are reported
>> instead of mcount.
>
>
> nm vmlinux | grep __fentry__
> nm vmlinux | grep mcount
>
> What do these report ? I bet you that in
On 18.12.2016 16:45, Jiri Slaby wrote:
> Moreover, with some modules, __put_user_1 and others are reported
> instead of mcount.
nm vmlinux | grep __fentry__
nm vmlinux | grep mcount
What do these report ? I bet you that in your vmlinux the first one
would return something like :
On 18.12.2016 16:45, Jiri Slaby wrote:
> Moreover, with some modules, __put_user_1 and others are reported
> instead of mcount.
nm vmlinux | grep __fentry__
nm vmlinux | grep mcount
What do these report ? I bet you that in your vmlinux the first one
would return something like :
On 12/18/2016, 02:27 PM, Nikolay Borisov wrote:
> This is the likely problem here.
No, it is not. How could a rpm be built with two compilers?
Moreover, with some modules, __put_user_1 and others are reported
instead of mcount.
--
js
suse labs
On 12/18/2016, 02:27 PM, Nikolay Borisov wrote:
> This is the likely problem here.
No, it is not. How could a rpm be built with two compilers?
Moreover, with some modules, __put_user_1 and others are reported
instead of mcount.
--
js
suse labs
On 18.12.2016 13:03, Arend Van Spriel wrote:
> On 18-12-2016 11:49, Jiri Slaby wrote:
>> On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
>>> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
Yes, disk drivers won't load:
[2.141973] virtio_pci: disagrees about
On 18.12.2016 13:03, Arend Van Spriel wrote:
> On 18-12-2016 11:49, Jiri Slaby wrote:
>> On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
>>> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
Yes, disk drivers won't load:
[2.141973] virtio_pci: disagrees about version of
On 18-12-2016 11:49, Jiri Slaby wrote:
> On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
>> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>>>
>>> Yes, disk drivers won't load:
>>> [2.141973] virtio_pci: disagrees about version of symbol mcount
>>> [2.144415]
On 18-12-2016 11:49, Jiri Slaby wrote:
> On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
>> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>>>
>>> Yes, disk drivers won't load:
>>> [2.141973] virtio_pci: disagrees about version of symbol mcount
>>> [2.144415] virtio_pci: Unknown
On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>>
>> Yes, disk drivers won't load:
>> [2.141973] virtio_pci: disagrees about version of symbol mcount
>> [2.144415] virtio_pci: Unknown symbol mcount (err -22)
>
> This
On 12/18/2016, 12:59 AM, Linus Torvalds wrote:
> On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>>
>> Yes, disk drivers won't load:
>> [2.141973] virtio_pci: disagrees about version of symbol mcount
>> [2.144415] virtio_pci: Unknown symbol mcount (err -22)
>
> This makes no sense.
>
On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>
> Yes, disk drivers won't load:
> [2.141973] virtio_pci: disagrees about version of symbol mcount
> [2.144415] virtio_pci: Unknown symbol mcount (err -22)
This makes no sense.
mcount isn't even one of the symbols that
On Sat, Dec 17, 2016 at 12:57 AM, Jiri Slaby wrote:
>
> Yes, disk drivers won't load:
> [2.141973] virtio_pci: disagrees about version of symbol mcount
> [2.144415] virtio_pci: Unknown symbol mcount (err -22)
This makes no sense.
mcount isn't even one of the symbols that the patch by
On Sat, Dec 17, 2016 at 09:57:47AM +0100, Jiri Slaby wrote:
> On 12/16/2016, 08:57 PM, Linus Torvalds wrote:
> > On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
> >>
> >> what happened to this? I had to apply this to fix 4.9-pae kernel here.
> >
> > Did you actually have to
On Sat, Dec 17, 2016 at 09:57:47AM +0100, Jiri Slaby wrote:
> On 12/16/2016, 08:57 PM, Linus Torvalds wrote:
> > On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
> >>
> >> what happened to this? I had to apply this to fix 4.9-pae kernel here.
> >
> > Did you actually have to do that?
>
>
On 12/16/2016, 08:57 PM, Linus Torvalds wrote:
> On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
>>
>> what happened to this? I had to apply this to fix 4.9-pae kernel here.
>
> Did you actually have to do that?
Yes, disk drivers won't load:
[2.141973] virtio_pci:
On 12/16/2016, 08:57 PM, Linus Torvalds wrote:
> On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
>>
>> what happened to this? I had to apply this to fix 4.9-pae kernel here.
>
> Did you actually have to do that?
Yes, disk drivers won't load:
[2.141973] virtio_pci: disagrees about
On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
>
> what happened to this? I had to apply this to fix 4.9-pae kernel here.
Did you actually have to do that?
Because a missing CRC shouldn't be fatal in 4.9.
What was the failure mode?
Linus
On Fri, Dec 16, 2016 at 11:55 AM, Jiri Slaby wrote:
>
> what happened to this? I had to apply this to fix 4.9-pae kernel here.
Did you actually have to do that?
Because a missing CRC shouldn't be fatal in 4.9.
What was the failure mode?
Linus
On 10/17/2016, 12:01 PM, Adam Borowski wrote:
> Anyway, here's my stab at x86:
Hi,
what happened to this? I had to apply this to fix 4.9-pae kernel here.
> From db746df65b920591606398b4b244f5b6dc9eea04 Mon Sep 17 00:00:00 2001
> From: Adam Borowski
> Date: Mon, 17 Oct 2016
On 10/17/2016, 12:01 PM, Adam Borowski wrote:
> Anyway, here's my stab at x86:
Hi,
what happened to this? I had to apply this to fix 4.9-pae kernel here.
> From db746df65b920591606398b4b244f5b6dc9eea04 Mon Sep 17 00:00:00 2001
> From: Adam Borowski
> Date: Mon, 17 Oct 2016 11:42:35 +0200
>
On Tue, Nov 01, 2016 at 04:48:48PM +0100, Michal Marek wrote:
> > Adam Borowski wrote:
> >
> >> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> +#include
> +#include
> >>>
> >>> Included twice.
> >>
> >> D'oh!
This appears to be the only
On Tue, Nov 01, 2016 at 04:48:48PM +0100, Michal Marek wrote:
> > Adam Borowski wrote:
> >
> >> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> +#include
> +#include
> >>>
> >>> Included twice.
> >>
> >> D'oh!
This appears to be the only thing to fix, right?
On 2016-10-18 03:34, Nicholas Piggin wrote:
> Hi Adam,
>
> Thanks, this is looking good. powerpc will be able to use the generic
> header.
>
> On Tue, 18 Oct 2016 02:16:26 +0200
> Adam Borowski wrote:
>
>> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
On 2016-10-18 03:34, Nicholas Piggin wrote:
> Hi Adam,
>
> Thanks, this is looking good. powerpc will be able to use the generic
> header.
>
> On Tue, 18 Oct 2016 02:16:26 +0200
> Adam Borowski wrote:
>
>> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
+#include
On 27.10.2016 10:10, Kalle Valo wrote:
> (Adding Thorsten because of a serious regression and Steven because he
> tried to fix something in the same commit)
Many thx.
I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to
On 27.10.2016 10:10, Kalle Valo wrote:
> (Adding Thorsten because of a serious regression and Steven because he
> tried to fix something in the same commit)
Many thx.
I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to
On Thu, 27 Oct 2016 11:10:03 +0300
Kalle Valo wrote:
> (Adding Thorsten because of a serious regression and Steven because he
> tried to fix something in the same commit)
>
> Nicholas Piggin writes:
>
> > On Wed, 19 Oct 2016 16:38:14 +0200
> > Michal
On Thu, 27 Oct 2016 11:10:03 +0300
Kalle Valo wrote:
> (Adding Thorsten because of a serious regression and Steven because he
> tried to fix something in the same commit)
>
> Nicholas Piggin writes:
>
> > On Wed, 19 Oct 2016 16:38:14 +0200
> > Michal Marek wrote:
> >
> >> Dne 18.10.2016 v
On Thu, 27 Oct 2016 16:14:28 +0300
Kalle Valo wrote:
> Nicholas Piggin writes:
>
> > On Thu, 27 Oct 2016 11:10:03 +0300
> > Kalle Valo wrote:
> >
> >> (Adding Thorsten because of a serious regression and Steven because he
> >>
On Thu, 27 Oct 2016 16:14:28 +0300
Kalle Valo wrote:
> Nicholas Piggin writes:
>
> > On Thu, 27 Oct 2016 11:10:03 +0300
> > Kalle Valo wrote:
> >
> >> (Adding Thorsten because of a serious regression and Steven because he
> >> tried to fix something in the same commit)
> >>
> >> Nicholas
(Adding Thorsten because of a serious regression and Steven because he
tried to fix something in the same commit)
Nicholas Piggin writes:
> On Wed, 19 Oct 2016 16:38:14 +0200
> Michal Marek wrote:
>
>> Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
>> >
(Adding Thorsten because of a serious regression and Steven because he
tried to fix something in the same commit)
Nicholas Piggin writes:
> On Wed, 19 Oct 2016 16:38:14 +0200
> Michal Marek wrote:
>
>> Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
>> > We should probably just bring all
Nicholas Piggin writes:
> On Thu, 27 Oct 2016 11:10:03 +0300
> Kalle Valo wrote:
>
>> (Adding Thorsten because of a serious regression and Steven because he
>> tried to fix something in the same commit)
>>
>> Nicholas Piggin writes:
Nicholas Piggin writes:
> On Thu, 27 Oct 2016 11:10:03 +0300
> Kalle Valo wrote:
>
>> (Adding Thorsten because of a serious regression and Steven because he
>> tried to fix something in the same commit)
>>
>> Nicholas Piggin writes:
>>
>> > On Wed, 19 Oct 2016 16:38:14 +0200
>> > Michal
On Wed, 19 Oct 2016 16:38:14 +0200
Michal Marek wrote:
> Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
> > We should probably just bring all these arch patches through the
> > kbuild tree.
> >
> > I'm sorry for the breakage: I didn't realize it broke the build with
> > some
On Wed, 19 Oct 2016 16:38:14 +0200
Michal Marek wrote:
> Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
> > We should probably just bring all these arch patches through the
> > kbuild tree.
> >
> > I'm sorry for the breakage: I didn't realize it broke the build with
> > some configs,
Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
> We should probably just bring all these arch patches through the
> kbuild tree.
>
> I'm sorry for the breakage: I didn't realize it broke the build with
> some configs, otherwise I would have given Michal a heads up before
> his pull request,
Dne 18.10.2016 v 03:34 Nicholas Piggin napsal(a):
> We should probably just bring all these arch patches through the
> kbuild tree.
>
> I'm sorry for the breakage: I didn't realize it broke the build with
> some configs, otherwise I would have given Michal a heads up before
> his pull request,
Hi Adam,
Thanks, this is looking good. powerpc will be able to use the generic
header.
On Tue, 18 Oct 2016 02:16:26 +0200
Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> > > +#include
> > > +#include
> >
> > Included twice.
Hi Adam,
Thanks, this is looking good. powerpc will be able to use the generic
header.
On Tue, 18 Oct 2016 02:16:26 +0200
Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> > > +#include
> > > +#include
> >
> > Included twice.
>
> D'oh!
>
> > >
On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> > +#include
> > +#include
>
> Included twice.
D'oh!
> > +#include
> > +#include
> > +#include
> > +
> > +#include
> > +
> > +#include
> > +#include
> > +#include
> > +#include
>
> No for __sw_hweight32 and
On Mon, Oct 17, 2016 at 02:22:34PM +0200, Mathieu OTHACEHE wrote:
> > +#include
> > +#include
>
> Included twice.
D'oh!
> > +#include
> > +#include
> > +#include
> > +
> > +#include
> > +
> > +#include
> > +#include
> > +#include
> > +#include
>
> No for __sw_hweight32 and
> +#include
> +#include
Included twice.
> +#include
> +#include
> +#include
> +
> +#include
> +
> +#include
> +#include
> +#include
> +#include
No for __sw_hweight32 and __sw_hweight64 ?
> +#include
> +#include
Included twice.
> +#include
> +#include
> +#include
> +
> +#include
> +
> +#include
> +#include
> +#include
> +#include
No for __sw_hweight32 and __sw_hweight64 ?
On Mon, Oct 17, 2016 at 2:17 PM, Geert Uytterhoeven
wrote:
> Hi Alexey,
>
> On Mon, Oct 17, 2016 at 1:12 PM, Alexey Dobriyan wrote:
>> On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
>>> On Mon, Oct 17, 2016 at 05:59:51PM
On Mon, Oct 17, 2016 at 2:17 PM, Geert Uytterhoeven
wrote:
> Hi Alexey,
>
> On Mon, Oct 17, 2016 at 1:12 PM, Alexey Dobriyan wrote:
>> On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
>>> On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
On Mon, 17 Oct 2016 08:51:31
Hi Alexey,
On Mon, Oct 17, 2016 at 1:12 PM, Alexey Dobriyan wrote:
> On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
>> On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
>>> On Mon, 17 Oct 2016 08:51:31 +0200
>>> Adam Borowski
Hi Alexey,
On Mon, Oct 17, 2016 at 1:12 PM, Alexey Dobriyan wrote:
> On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
>> On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
>>> On Mon, 17 Oct 2016 08:51:31 +0200
>>> Adam Borowski wrote:
>
>> --- /dev/null
>> +++
On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
>> On Mon, 17 Oct 2016 08:51:31 +0200
>> Adam Borowski wrote:
> --- /dev/null
> +++ b/include/asm-generic/asm-prototypes.h
> @@ -0,0
On Mon, Oct 17, 2016 at 1:01 PM, Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
>> On Mon, 17 Oct 2016 08:51:31 +0200
>> Adam Borowski wrote:
> --- /dev/null
> +++ b/include/asm-generic/asm-prototypes.h
> @@ -0,0 +1,7 @@
> +#include
> +extern void
On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
> On Mon, 17 Oct 2016 08:51:31 +0200
> Adam Borowski wrote:
> > On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> > > On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval
> >
On Mon, Oct 17, 2016 at 05:59:51PM +1100, Nicholas Piggin wrote:
> On Mon, 17 Oct 2016 08:51:31 +0200
> Adam Borowski wrote:
> > On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> > > On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval
> > > wrote:
> > > > So this has broken all
On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval wrote:
> > On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> > > please pull these kbuild changes for v4.9-rc1:
> > >
> > > - EXPORT_SYMBOL for
On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval wrote:
> > On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> > > please pull these kbuild changes for v4.9-rc1:
> > >
> > > - EXPORT_SYMBOL for asm source by Al Viro.
On Mon, 17 Oct 2016 08:51:31 +0200
Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> > On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval
> > wrote:
> > > On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek
On Mon, 17 Oct 2016 08:51:31 +0200
Adam Borowski wrote:
> On Mon, Oct 17, 2016 at 02:57:09PM +1100, Nicholas Piggin wrote:
> > On Sat, 15 Oct 2016 17:22:05 -0700 Omar Sandoval
> > wrote:
> > > On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> > > > please pull these kbuild
Hi,
>> Reverting 784d5699eddc ("x86: move exports to actual definitions") fixes
>> it for me. This is with GCC 6.2.1, binutils 2.27, attached config.
I've had the same problem. Reverting your binutils from 2.27 to 2.26,
will also fix it. It seems ld 2.27 is not merging weak symbols from .o
Hi,
>> Reverting 784d5699eddc ("x86: move exports to actual definitions") fixes
>> it for me. This is with GCC 6.2.1, binutils 2.27, attached config.
I've had the same problem. Reverting your binutils from 2.27 to 2.26,
will also fix it. It seems ld 2.27 is not merging weak symbols from .o
On Sat, 15 Oct 2016 17:22:05 -0700
Omar Sandoval wrote:
> On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> > Hi Linus,
> >
> > please pull these kbuild changes for v4.9-rc1:
> >
> > - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression,
> >
On Sat, 15 Oct 2016 17:22:05 -0700
Omar Sandoval wrote:
> On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> > Hi Linus,
> >
> > please pull these kbuild changes for v4.9-rc1:
> >
> > - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression,
> > because genksyms
On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> Hi Linus,
>
> please pull these kbuild changes for v4.9-rc1:
>
> - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression,
> because genksyms no longer generates checksums for these symbols
> (CONFIG_MODVERSIONS).
On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote:
> Hi Linus,
>
> please pull these kbuild changes for v4.9-rc1:
>
> - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression,
> because genksyms no longer generates checksums for these symbols
> (CONFIG_MODVERSIONS).
64 matches
Mail list logo