From: hch@lst.de (hch@lst.de)
To: linux-snps-arc@lists.infradead.org
Subject: dma-mapping: clearing GFP_ZERO flag caused crashes of Ethernet on arc/hsdk board.
Date: Wed, 28 Mar 2018 09:53:13 +0200 [thread overview]
Message-ID: <20180328075313.GA19864@lst.de> (raw)
In-Reply-To: <1522185558.6917.7.camel@synopsys.com>
> > The logical question is why?
>
> 1. See that's another platform with ARC core so maybe in case of ARM
> DMA allocator already zeroes pages regardless provided flags -
> personally I didn't check that.
Yes, most architectures always clear memory returned by dma_alloc*.
Looks like a few don't and my commit got them in trouble. As usual
I'd prefer to match x86 semantics for now to avoid problems.
I'll send patches for arc and s390 which seem to be actually used
holdouts, and will look if anyone else is also affected.
prev parent reply other threads:[~2018-03-28 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 17:12 dma-mapping: clearing GFP_ZERO flag caused crashes of Ethernet on arc/hsdk board Evgeniy Didin
2018-03-27 18:11 ` Andy Shevchenko
2018-03-27 18:24 ` Vineet Gupta
2018-03-27 21:19 ` Alexey Brodkin
2018-03-28 7:53 ` hch [this message]
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=20180328075313.GA19864@lst.de \
--to=hch@lst.de \
--cc=linux-snps-arc@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 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).