From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: nm127-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org,
eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
urs.thuermann-l29pVbxQd1IUtdQbppsyvg@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
oliver.hartkopp-l29pVbxQd1IUtdQbppsyvg@public.gmane.org
Subject: Re: Linux 2.6.34-rc3 + CAN build problem
Date: Sun, 11 Apr 2010 20:53:56 +0200 [thread overview]
Message-ID: <4BC21AC4.8060403@hartkopp.net> (raw)
In-Reply-To: <20100410.155009.66184583.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
David Miller wrote:
> From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
> 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
next prev parent reply other threads:[~2010-04-11 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 8:13 Linux 2.6.34-rc3 + CAN build problem Németh Márton
2010-04-10 9:47 ` Eric Dumazet
2010-04-10 10:36 ` Németh Márton
[not found] ` <4BC054AE.7040303-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2010-04-10 12:36 ` Oliver Hartkopp
2010-04-10 22:50 ` David Miller
2010-04-11 5:14 ` Németh Márton
2010-04-11 5:16 ` David Miller
[not found] ` <20100410.155009.66184583.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-04-11 18:53 ` Oliver Hartkopp [this message]
2010-04-11 20:19 ` David Miller
2010-04-10 22:48 ` David Miller
2010-04-13 10:09 ` David Miller
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=4BC21AC4.8060403@hartkopp.net \
--to=socketcan-fj+pqtutwrtk1umjsbkqmq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nm127-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org \
--cc=oliver.hartkopp-l29pVbxQd1IUtdQbppsyvg@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=urs.thuermann-l29pVbxQd1IUtdQbppsyvg@public.gmane.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).