All of lore.kernel.org
 help / color / mirror / Atom feed
From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel build error
Date: Sun, 17 Mar 2013 08:28:19 -0700	[thread overview]
Message-ID: <20130317152819.GA12313@gmail.com> (raw)

I'm facing a kernel build issue with the latest kernel on my machine. It seem
like a configuration issue, and I haven't been able to resolve it for sometime,
hence need your help. The error message is as below:

<error snip>
ERROR: "copy_from_user_overflow" [net/core/pktgen.ko] undefined!
ERROR: "copy_from_user_overflow" [fs/binfmt_misc.ko] undefined!
ERROR: "copy_from_user_overflow" [drivers/staging/cxt1e1/cxt1e1.ko] undefined!
ERROR: "copy_from_user_overflow" [drivers/isdn/icn/icn.ko] undefined!
ERROR: "copy_from_user_overflow" [drivers/isdn/hardware/avm/b1.ko] undefined!
<error snip>

The subroutine "copy_from_user_overflow" is defined in lib/usercopy.c, and the
'Makefile' in the lib directory looks something like this:
<snip from lib/Makefile>
lib-$(CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS) += usercopy.o
<snip from lib/Makefile>

I think that this config option should be a built-in ('y') and I see that this 
config option is indeed set to 'y' in the .config file.
<snip from .config>
amit at ubuntu:~/linux-next/linux-next$ grep
CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS .config
CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS=y
<snip from .config>

So what am I missing here ?

Some information about my git tree:
amit at ubuntu:~/linux-next/linux-next$ git remote show origin
* remote origin
  Fetch URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

amit at ubuntu:~/linux-next/linux-next$ git tag -l next-*|tail -n 1
next-20130314 <--- latest tag

amit@ubuntu:~/linux-next/linux-next$ git branch
* 15-March <--- --  branch based on the latest tag
  22-Feb-13

-Amit

             reply	other threads:[~2013-03-17 15:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 15:28 Kumar amit mehta [this message]
2013-03-18  4:21 ` kernel build error Mulyadi Santosa
2013-03-19  5:28   ` Kumar amit mehta
2013-03-19 14:43     ` Mulyadi Santosa
2013-03-20  6:56       ` Kumar amit mehta
2013-03-20  7:07         ` Kumar amit mehta
2013-03-20  9:48           ` Ben Wu
2013-03-20  9:49           ` wake_lock in linux kernel Ben Wu
2013-03-21  4:34             ` Yuva Raj
2013-03-20 17:32           ` kernel build error Valdis.Kletnieks at vt.edu
2013-03-21  6:16           ` Kumar amit mehta
2013-03-22  3:41             ` Mulyadi Santosa
2013-03-22 10:17               ` Kumar amit mehta
2013-03-24  5:49                 ` Mulyadi Santosa
2013-03-25  5:04                   ` Kumar amit mehta
2013-03-25  7:36                     ` Mulyadi Santosa
     [not found]                   ` <20130331044544.GA3291@gmail.com>
2013-04-02  3:04                     ` Mulyadi Santosa
2013-04-02  6:19                       ` Kumar amit mehta
2013-04-02 13:40                         ` Mulyadi Santosa
  -- strict thread matches above, loose matches on Subject: below --
2019-08-22 12:27 Kernel " James David Lyons
2016-04-26  6:30 Kernel Build error Harinath maddelal
2016-04-26  6:43 ` Khem Raj
2016-04-26  7:10   ` Harinath maddelal
2016-04-26 14:17     ` Khem Raj
2005-05-12 22:30 Kernel build error mcnernbm

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=20130317152819.GA12313@gmail.com \
    --to=gmate.amit@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.