All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	"linux-m68k@lists.linux-m68k.org"
	<linux-m68k@lists.linux-m68k.org>,
	"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	"openrisc@lists.librecores.org" <openrisc@lists.librecores.org>,
	"ashutosh.dixit@intel.com" <ashutosh.dixit@intel.com>,
	"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 12:12:00 +0000	[thread overview]
Message-ID: <1544789518.3270.34.camel@synopsys.com> (raw)
In-Reply-To: <20181214082515.14835-2-hch@lst.de>

Hi Christoph,

do you have any public git repository with all your dma changes?

I want to test them for ARC.

Thanks.

On Fri, 2018-12-14 at 09:25 +0100, Christoph Hellwig wrote:
> If we want to map memory from the DMA allocator to userspace it must be
> zeroed at allocation time to prevent stale data leaks.   We already do
> this on most common architectures, but some architectures don't do this
> yet, fix them up, either by passing GFP_ZERO when we use the normal page
> allocator or doing a manual memset otherwise.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
-- 
 Eugeniy Paltsev

WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: "hch@lst.de" <hch@lst.de>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	"linux-m68k@lists.linux-m68k.org"
	<linux-m68k@lists.linux-m68k.org>,
	"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"openrisc@lists.librecores.org" <openrisc@lists.librecores.org>,
	"ashutosh.dixit@intel.com" <ashutosh.dixit@intel.com>,
	"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 12:12:00 +0000	[thread overview]
Message-ID: <1544789518.3270.34.camel@synopsys.com> (raw)
In-Reply-To: <20181214082515.14835-2-hch@lst.de>

SGkgQ2hyaXN0b3BoLA0KDQpkbyB5b3UgaGF2ZSBhbnkgcHVibGljIGdpdCByZXBvc2l0b3J5IHdp
dGggYWxsIHlvdXIgZG1hIGNoYW5nZXM/DQoNCkkgd2FudCB0byB0ZXN0IHRoZW0gZm9yIEFSQy4N
Cg0KVGhhbmtzLg0KDQpPbiBGcmksIDIwMTgtMTItMTQgYXQgMDk6MjUgKzAxMDAsIENocmlzdG9w
aCBIZWxsd2lnIHdyb3RlOg0KPiBJZiB3ZSB3YW50IHRvIG1hcCBtZW1vcnkgZnJvbSB0aGUgRE1B
IGFsbG9jYXRvciB0byB1c2Vyc3BhY2UgaXQgbXVzdCBiZQ0KPiB6ZXJvZWQgYXQgYWxsb2NhdGlv
biB0aW1lIHRvIHByZXZlbnQgc3RhbGUgZGF0YSBsZWFrcy4gICBXZSBhbHJlYWR5IGRvDQo+IHRo
aXMgb24gbW9zdCBjb21tb24gYXJjaGl0ZWN0dXJlcywgYnV0IHNvbWUgYXJjaGl0ZWN0dXJlcyBk
b24ndCBkbyB0aGlzDQo+IHlldCwgZml4IHRoZW0gdXAsIGVpdGhlciBieSBwYXNzaW5nIEdGUF9a
RVJPIHdoZW4gd2UgdXNlIHRoZSBub3JtYWwgcGFnZQ0KPiBhbGxvY2F0b3Igb3IgZG9pbmcgYSBt
YW51YWwgbWVtc2V0IG90aGVyd2lzZS4NCj4gDQo+IFNpZ25lZC1vZmYtYnk6IENocmlzdG9waCBI
ZWxsd2lnIDxoY2hAbHN0LmRlPg0KPiAtLS0NCi0tIA0KIEV1Z2VuaXkgUGFsdHNldg=

WARNING: multiple messages have this Message-ID (diff)
From: eugeniy.paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 12:12:00 +0000	[thread overview]
Message-ID: <1544789518.3270.34.camel@synopsys.com> (raw)
In-Reply-To: <20181214082515.14835-2-hch@lst.de>

Hi Christoph,

do you have any public git repository with all your dma changes?

I want to test them for ARC.

Thanks.

On Fri, 2018-12-14@09:25 +0100, Christoph Hellwig wrote:
> If we want to map memory from the DMA allocator to userspace it must be
> zeroed at allocation time to prevent stale data leaks.   We already do
> this on most common architectures, but some architectures don't do this
> yet, fix them up, either by passing GFP_ZERO when we use the normal page
> allocator or doing a manual memset otherwise.
> 
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
-- 
 Eugeniy Paltsev

WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 12:12:00 +0000	[thread overview]
Message-ID: <1544789518.3270.34.camel@synopsys.com> (raw)
In-Reply-To: <20181214082515.14835-2-hch@lst.de>

Hi Christoph,

do you have any public git repository with all your dma changes?

I want to test them for ARC.

Thanks.

On Fri, 2018-12-14 at 09:25 +0100, Christoph Hellwig wrote:
> If we want to map memory from the DMA allocator to userspace it must be
> zeroed at allocation time to prevent stale data leaks.   We already do
> this on most common architectures, but some architectures don't do this
> yet, fix them up, either by passing GFP_ZERO when we use the normal page
> allocator or doing a manual memset otherwise.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
-- 
 Eugeniy Paltsev

  parent reply	other threads:[~2018-12-14 12:26 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  8:25 ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14  8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
2018-12-14  8:25   ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  9:54   ` Geert Uytterhoeven
2018-12-14  9:54     ` [OpenRISC] " Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:55     ` Geert Uytterhoeven
2018-12-14  9:55       ` [OpenRISC] " Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14 11:47     ` Christoph Hellwig
2018-12-14 11:47       ` [OpenRISC] " Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 12:36       ` Geert Uytterhoeven
2018-12-14 12:36         ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 12:36         ` Geert Uytterhoeven
2018-12-14 12:36         ` Geert Uytterhoeven
2018-12-14 14:14       ` Greg Ungerer
2018-12-14 14:14         ` [OpenRISC] " Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-17 11:59         ` Christoph Hellwig
2018-12-17 11:59           ` [OpenRISC] " Christoph Hellwig
2018-12-17 11:59           ` Christoph Hellwig
2018-12-17 11:59           ` Christoph Hellwig
2019-01-11  6:09           ` Greg Ungerer
2018-12-14 12:12   ` Eugeniy Paltsev [this message]
2018-12-14 12:12     ` [OpenRISC] " Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:21     ` hch
2018-12-14 12:21       ` [OpenRISC] " hch
2018-12-14 12:21       ` hch-jcswGhMUV9g
2018-12-14 12:21       ` hch
2018-12-14 12:21       ` hch
2018-12-14 18:10   ` Sam Ravnborg
2018-12-14 18:10     ` [OpenRISC] " Sam Ravnborg
2018-12-14 18:10     ` Sam Ravnborg
2018-12-14 18:10     ` Sam Ravnborg
2018-12-14 18:35     ` Christoph Hellwig
2018-12-14 18:35       ` [OpenRISC] " Christoph Hellwig
2018-12-14 18:35       ` Christoph Hellwig
2018-12-14 18:35       ` Christoph Hellwig
2018-12-14  8:25 ` [PATCH 2/2] dma-mapping: deprecate dma_zalloc_coherent Christoph Hellwig
2018-12-14  8:25   ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14 13:33 ` ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 13:33   ` [OpenRISC] " Christoph Hellwig
2018-12-14 13:33   ` Christoph Hellwig
2018-12-14 13:33   ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59   ` [OpenRISC] " Christoph Hellwig
2018-12-19 16:59   ` Christoph Hellwig
2018-12-19 16:59   ` Christoph Hellwig
2018-12-20 14:32   ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:34     ` hch
2018-12-20 14:34       ` [OpenRISC] " hch
2018-12-20 14:34       ` hch
2018-12-20 14:34       ` hch
2018-12-20 14:34       ` hch
2018-12-20 14:39       ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:46         ` hch
2018-12-20 14:46           ` [OpenRISC] " hch
2018-12-20 14:46           ` hch
2018-12-20 14:46           ` hch
2018-12-20 14:46           ` hch
2018-12-20 17:37           ` hch
2018-12-20 17:37             ` [OpenRISC] " hch
2018-12-20 17:37             ` hch
2018-12-20 17:37             ` hch
2018-12-20 17:37             ` hch

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=1544789518.3270.34.camel@synopsys.com \
    --to=eugeniy.paltsev@synopsys.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=monstr@monstr.eu \
    --cc=openrisc@lists.librecores.org \
    --cc=sparclinux@vger.kernel.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.