All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Data corruption on i.MX6 IPU in arm_copy_from_user()
Date: Wed, 26 May 2021 14:29:07 +0200	[thread overview]
Message-ID: <m3r1htu19o.fsf@t19.piap.pl> (raw)
In-Reply-To: <20210526100843.GD30436@shell.armlinux.org.uk> (Russell King's message of "Wed, 26 May 2021 11:08:44 +0100")

"Russell King (Oracle)" <linux@armlinux.org.uk> writes:

> Surely someone is not using copy_*_user() to copy data from userspace
> direct to MMIO space... that would be crazy.

No, it's the other way around: reading MMIO mapped to userspace (mmap
on /dev/mem) and copying it to simple kernel buffer (e.g. pipe buffer).
I.e., the MMIO is the userspace here (thus copy_from_user()).
-- 
Krzysztof Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa

WARNING: multiple messages have this Message-ID (diff)
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	 lkml <linux-kernel@vger.kernel.org>
Subject: Re: Data corruption on i.MX6 IPU in arm_copy_from_user()
Date: Wed, 26 May 2021 14:29:07 +0200	[thread overview]
Message-ID: <m3r1htu19o.fsf@t19.piap.pl> (raw)
In-Reply-To: <20210526100843.GD30436@shell.armlinux.org.uk> (Russell King's message of "Wed, 26 May 2021 11:08:44 +0100")

"Russell King (Oracle)" <linux@armlinux.org.uk> writes:

> Surely someone is not using copy_*_user() to copy data from userspace
> direct to MMIO space... that would be crazy.

No, it's the other way around: reading MMIO mapped to userspace (mmap
on /dev/mem) and copying it to simple kernel buffer (e.g. pipe buffer).
I.e., the MMIO is the userspace here (thus copy_from_user()).
-- 
Krzysztof Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-26 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  8:26 Data corruption on i.MX6 IPU in arm_copy_from_user() Krzysztof Hałasa
2021-05-26  8:26 ` Krzysztof Hałasa
2021-05-26 10:08 ` Russell King (Oracle)
2021-05-26 10:08   ` Russell King (Oracle)
2021-05-26 12:29   ` Krzysztof Hałasa [this message]
2021-05-26 12:29     ` Krzysztof Hałasa
2021-05-26 13:18     ` Russell King (Oracle)
2021-05-26 13:18       ` Russell King (Oracle)
2021-05-27 14:06       ` David Laight
2021-05-27 14:06         ` David Laight
2021-05-28 10:02       ` Krzysztof Hałasa
2021-05-28 10:02         ` Krzysztof Hałasa
2021-05-28 14:35         ` Russell King (Oracle)
2021-05-28 14:35           ` Russell King (Oracle)
2021-05-31  4:30           ` Krzysztof Hałasa
2021-05-31  4:30             ` Krzysztof Hałasa
2021-05-31  6:20           ` Krzysztof Hałasa
2021-05-31  6:20             ` Krzysztof Hałasa

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=m3r1htu19o.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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.