linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Hector Martin <marcan@marcan.st>, Clemens Ladisch <clemens@ladisch.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire-ohci: work around oversized DMA reads on JMicron controllers
Date: Sun, 12 Nov 2017 22:05:29 +0100	[thread overview]
Message-ID: <20171112220529.4cf6c5b5@kant> (raw)
In-Reply-To: <554bac12-e021-2541-6812-ae9a4e0c96ba@ladisch.de>

On Nov 03 Clemens Ladisch wrote:
> Hector Martin wrote:
> > At least some JMicron controllers issue buggy oversized DMA reads when
> > fetching context descriptors, always fetching 0x20 bytes at once for
> > descriptors which are only 0x10 bytes long. This is often harmless, but
> > can cause page faults on modern systems with IOMMUs:
> >
> > DMAR: [DMA Read] Request device [05:00.0] fault addr fff56000 [fault reason 06] PTE Read access is not set
> > firewire_ohci 0000:05:00.0: DMA context IT0 has stopped, error code: evt_descriptor_read
> >
> > This works around the problem by always leaving 0x10 padding bytes at
> > the end of descriptor buffer pages, which should be harmless to do
> > unconditionally for controllers in case others have the same behavior.
> >
> > Signed-off-by: Hector Martin <marcan@marcan.st>  
> 
> Reviewed-by: Clemens Ladisch <clemens@ladisch.de>

Thanks Hector for the troubleshooting and for the patch.
Thanks Clemens for the review.

It's been a while since I last reviewed and tested kernel patches, and
also my main FireWire equipped PC is currently tied up in work for which
reboots aren't desirable.  But I am updating a long unused secondary
FireWire'd PC right now and give the patch some testing this week.  (This
one even has a JMicron controller, but not an IOMMU.)

> > ---
> >  drivers/firewire/ohci.c | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/firewire/ohci.c b/drivers/firewire/ohci.c
> > index 8bf89267dc25..d731b413cb2c 100644
> > --- a/drivers/firewire/ohci.c
> > +++ b/drivers/firewire/ohci.c
> > @@ -1130,7 +1130,13 @@ static int context_add_buffer(struct context *ctx)
> >  		return -ENOMEM;
> >
> >  	offset = (void *)&desc->buffer - (void *)desc;
> > -	desc->buffer_size = PAGE_SIZE - offset;
> > +	/*
> > +	 * Some controllers, like JMicron ones, always issue 0x20-byte DMA reads
> > +	 * for descriptors, even 0x10-byte ones. This can cause page faults when
> > +	 * an IOMMU is in use and the oversized read crosses a page boundary.
> > +	 * Work around this by always leaving at least 0x10 bytes of padding.
> > +	 */
> > +	desc->buffer_size = PAGE_SIZE - offset - 0x10;
> >  	desc->buffer_bus = bus_addr + offset;
> >  	desc->used = 0;
> >  
-- 
Stefan Richter
-======----= =-== -==--
http://arcgraph.de/sr/

  reply	other threads:[~2017-11-12 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 11:28 [PATCH] firewire-ohci: work around oversized DMA reads on JMicron controllers Hector Martin
2017-11-03 14:21 ` Clemens Ladisch
2017-11-12 21:05   ` Stefan Richter [this message]
2018-01-11  2:31     ` Hector Martin 'marcan'
2018-01-13 16:55       ` Stefan Richter

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=20171112220529.4cf6c5b5@kant \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=marcan@marcan.st \
    /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).