From: Guenter Roeck <linux@roeck-us.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org, Rich Felker <dalias@libc.org>
Subject: Re: Runtime failure running sh:qemu in -next due to 'sh: fix copy_from_user()'
Date: Fri, 16 Sep 2016 20:32:05 +0000 [thread overview]
Message-ID: <20160916203205.GA29660@roeck-us.net> (raw)
In-Reply-To: <20160916200320.GZ2356@ZenIV.linux.org.uk>
On Fri, Sep 16, 2016 at 09:03:20PM +0100, Al Viro wrote:
> On Fri, Sep 16, 2016 at 12:12:18PM -0700, Guenter Roeck wrote:
> > Hi,
> >
> > I see the following runtime failure when running a 'sh' image with qemu in -next.
> >
> > [ ... ]
> >
> > sd 0:0:0:0: [sda] Attached SCSI disk
> > EXT2-fs (sda): warning: mounting unchecked fs, running e2fsck is recommended
> > VFS: Mounted root (ext2 filesystem) on device 8:0.
> > Freeing unused kernel memory: 124K (8c48a000 - 8c4a9000)
> > This architecture does not have kernel memory protection.
> > random: fast init done
> > Starting logging: OK
> > usb 1-1: new full-speed USB device number 2 using sm501-usb
> > Initializing random number generator... done.
> > Starting network...
> > ip: OVERRUN: Invalid argument
> > ip: OVERRUN: Bad address
> > ip: OVERRUN: Bad address
> > ip: OVERRUN: Bad address
> > ip: OVERRUN: Bad address
> > [repeats until the test aborts]
> >
> > Bisect points to commit 6e050503a150 ("sh: fix copy_from_user()"). Bisect log is
> > attached.
>
> BTW, could you post your .config and information about your userland? E.g.
> is that ip(8) a busybox one, etc. If it's busybox, this smells like EINVAL
> and EFAULT resp. coming from recvmsg() on netlink sockets, with nothing
> extraordinary in iovecs, AFAICS...
Please see https://github.com/groeck/linux-build-test/tree/master/rootfs/sh.
The rootfs is some three years old. I don't remember how I created it :-).
Guenter
next prev parent reply other threads:[~2016-09-16 20:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 19:12 Runtime failure running sh:qemu in -next due to 'sh: fix copy_from_user()' Guenter Roeck
2016-09-16 19:45 ` Al Viro
2016-09-16 20:59 ` Guenter Roeck
2016-09-16 21:31 ` Al Viro
2016-09-16 21:39 ` Rich Felker
2016-09-16 22:47 ` Guenter Roeck
2016-09-16 23:32 ` Rich Felker
2016-09-17 2:23 ` Guenter Roeck
2016-09-18 4:40 ` Rob Landley
2016-09-18 15:17 ` Rich Felker
2016-09-29 2:36 ` Rob Landley
2016-09-17 2:28 ` Guenter Roeck
2016-09-16 22:47 ` Guenter Roeck
2016-09-16 23:00 ` Al Viro
2016-09-16 20:03 ` Al Viro
2016-09-16 20:32 ` Guenter Roeck [this message]
2016-09-16 20:43 ` Lennart Sorensen
2016-09-16 21:20 ` Al Viro
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=20160916203205.GA29660@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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).