From: Kalle Valo <email@example.com>
To: Christian Lamparter <firstname.lastname@example.org>
Cc: Jia-Ju Bai <email@example.com>,
Subject: Re: [PATCH] p54: avoid accessing the data mapped to streaming DMA
Date: Wed, 26 Aug 2020 19:02:43 +0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Christian Lamparter's message of "Tue, 18 Aug 2020 19:27:10 +0200")
Christian Lamparter <firstname.lastname@example.org> writes:
> On 2020-08-02 15:29, Jia-Ju Bai wrote:
>> In p54p_tx(), skb->data is mapped to streaming DMA on line 337:
>> mapping = pci_map_single(..., skb->data, ...);
>> Then skb->data is accessed on line 349:
>> desc->device_addr = ((struct p54_hdr *)skb->data)->req_id;
>> This access may cause data inconsistency between CPU cache and hardware.
>> To fix this problem, ((struct p54_hdr *)skb->data)->req_id is stored in
>> a local variable before DMA mapping, and then the driver accesses this
>> local variable instead of skb->data.
> Interesting. Please bear with me here. From my understanding, the
> streaming direction is set to PCI_DMA_TODEVICE. So is it really
> possible for the hardware to interfere with the data without the IOMMU
> catching this?
Also is there any documentation about this scenario? I would like to
understand this better.
> (That said, patch looks be fine. I'll need to dust off a old PCI PC to
> check this with real hardware, if requested.)
No need to test with real hardware for my sake, but a careful review is
very much appreciated.
next prev parent reply other threads:[~2020-08-26 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 13:29 [PATCH] p54: avoid accessing the data mapped to streaming DMA Jia-Ju Bai
2020-08-18 12:41 ` Kalle Valo
2020-08-18 17:27 ` Christian Lamparter
2020-08-26 16:02 ` Kalle Valo [this message]
2020-08-28 21:19 ` Christian Lamparter
2020-08-31 14:00 ` Kalle Valo
2020-09-01 9:34 ` Kalle Valo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).