Prev: Probing System calls
Next: 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out
From: David Miller on 10 Apr 2010 19:00
From: Oliver Hartkopp <socketcan(a)hartkopp.net>
Date: Sat, 10 Apr 2010 14:36:48 +0200

> So i wonder why Nemeth trapped into this problem ... probably an include file
> mix-up?

Do you have CONFIG_DEBUG_STRICT_USER_COPY_CHECKS enabled in your
kernel config?

That's the only way you get an actual failure of a build when
the user copy size can't be proven to be in range by the
compiler, otherwise it just warns.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Miller on 11 Apr 2010 01:20
From: N�meth M�rton <nm127(a)freemail.hu>
Date: Sun, 11 Apr 2010 07:14:47 +0200

> David Miller wrote:
>> From: Oliver Hartkopp <socketcan(a)hartkopp.net>
>> Date: Sat, 10 Apr 2010 14:36:48 +0200
>>
>>> So i wonder why Nemeth trapped into this problem ... probably an include file
>>> mix-up?
>>
>> Do you have CONFIG_DEBUG_STRICT_USER_COPY_CHECKS enabled in your
>> kernel config?
>
> CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y

Just turn that off in your builds, it's for developers who want
to work on correcting those warnings, not you :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Németh Márton on 11 Apr 2010 01:20
David Miller wrote:
> From: Oliver Hartkopp <socketcan(a)hartkopp.net>
> Date: Sat, 10 Apr 2010 14:36:48 +0200
>
>> So i wonder why Nemeth trapped into this problem ... probably an include file
>> mix-up?
>
> Do you have CONFIG_DEBUG_STRICT_USER_COPY_CHECKS enabled in your
> kernel config?

CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y

> That's the only way you get an actual failure of a build when
> the user copy size can't be proven to be in range by the
> compiler, otherwise it just warns.
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Oliver Hartkopp on 11 Apr 2010 15:00
David Miller wrote:
> From: Oliver Hartkopp <socketcan(a)hartkopp.net>
> Date: Sat, 10 Apr 2010 14:36:48 +0200
>
>> So i wonder why Nemeth trapped into this problem ... probably an include file
>> mix-up?
>
> Do you have CONFIG_DEBUG_STRICT_USER_COPY_CHECKS enabled in your
> kernel config?
>
> That's the only way you get an actual failure of a build when
> the user copy size can't be proven to be in range by the
> compiler, otherwise it just warns.

No, indeed i do not have it set.

# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set

What would be the best approach to fix this build failure then?

By applying the patch thankfully provided by Eric?

Regards,
Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Miller on 11 Apr 2010 16:20
From: Oliver Hartkopp <socketcan(a)hartkopp.net>
Date: Sun, 11 Apr 2010 20:53:56 +0200

> By applying the patch thankfully provided by Eric?

I'll probably do that, yes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Probing System calls
Next: 2.6.34-rc3: eth0 (8139too): transmit queue 0 timed out