From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)
Date: Mon, 5 Mar 2018 15:28:46 +0100 [thread overview]
Message-ID: <20180305142846.GJ25189@lunn.ch> (raw)
In-Reply-To: <20180304204115.GD21710@lunn.ch>
On Sun, Mar 04, 2018 at 09:41:15PM +0100, Andrew Lunn wrote:
> On Sun, Mar 04, 2018 at 06:41:57PM +0100, Martin Michlmayr wrote:
> > A Debian user reported the following issue on QNAP TS-119P II with
> > 4.9.65:
> >
> > * Menno Finlay-Smits <inbox@menno.io> [2018-01-21 23:08]:
> > > Rsyncing files between 2 HDDs on a QNAP 119p with a fresh, minimal install of
> > > stretch NAS (armel) causes the kernel to fail after ~20mins with a kernel
> > > memory overwrite attempt (full error below).
>
> Please can you give me the exact rsync command being used. Having a
> unix domain socket seems a bit odd for rsync'ing files on the same
> machine.
I played with this a bit. When you rsync with both source and target
on the same machine, it appears to fork two processes, and connect
them together via a unix domain socket.
I tried reproducing this with 4.9.86. I used the command
rsync -az /home /root/home
which copied 12G of data. No problems seen. But this is one disk. I
assume the machine giving the problem has one of the disks as USB,
since the QNAP TS-119P II is a single bay NAS. So it could be the USB
disk is slower than the internal disk, and there is a backlog building
up. First a backlog for writing out to the disk, then a backlog
forming on the Unix domain socket? So maybe that is why i cannot
reproduce it. Or the problem has been fixed between 4.9.65 and 4.9.86.
Would it be possible to try to reproduce this problem with 4.9.86 on
the hardware reporting the issue?
Thanks
Andrew
next prev parent reply other threads:[~2018-03-05 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151652931598.757.4527606947579667082.reportbug@massive.lan>
2018-03-04 17:41 ` Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM) Martin Michlmayr
2018-03-04 18:42 ` Andrew Lunn
2018-03-04 20:41 ` Andrew Lunn
2018-03-05 14:28 ` Andrew Lunn [this message]
2018-03-05 15:57 ` Yves-Alexis Perez
2018-03-06 0:54 ` Menno Finlay-Smits
2018-03-07 3:58 ` Menno Finlay-Smits
2018-03-07 13:02 ` Andrew Lunn
2018-03-07 13:36 ` Andrew Lunn
2018-03-07 20:49 ` Menno Finlay-Smits
2018-03-07 22:27 ` Andrew Lunn
2018-03-09 9:53 ` Menno Finlay-Smits
2018-03-09 9:56 ` Yves-Alexis Perez
2018-03-09 14:27 ` Andrew Lunn
2018-03-11 11:02 ` Menno Finlay-Smits
2018-03-11 11:06 ` Yves-Alexis Perez
2018-03-11 20:59 ` Menno Finlay-Smits
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=20180305142846.GJ25189@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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.