From: corsac@debian.org (Yves-Alexis Perez)
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: Sun, 11 Mar 2018 12:06:31 +0100 [thread overview]
Message-ID: <1520766391.3566.7.camel@debian.org> (raw)
In-Reply-To: <1520766137.2953662.1298951624.71C28713@webmail.messagingengine.com>
On Mon, 2018-03-12 at 00:02 +1300, Menno Finlay-Smits wrote:
> Bingo. The problem doesn't seem to happen using linux-image-4.14.0-3-
> marvell_4.14.17-1 from sid. I've now successfully transferred 1.5TB from an
> external USB drive onto the internal hard disk. Previously the problem would
> show up within the first few 100MB of the transfer.
>
> Do you want me to help figure out which change to the kernel fixed the
> problem?
As far as I can tell and if I'm not mistaken, the fix is already identified
and is included in 4.9.86.
I've started working on it for Stretch, and at one point it will be uploaded
to -proposed-updates for inclusion in the next point release (9.5). When it's
done I'll probably ask you to try a test kernel to make sure it's really
fixed.
Regards,
--
Yves-Alexis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180311/9575cd85/attachment.sig>
next prev parent reply other threads:[~2018-03-11 11:06 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
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 [this message]
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=1520766391.3566.7.camel@debian.org \
--to=corsac@debian.org \
--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.