All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "hch@lst.de" <hch@lst.de>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"sebott@linux.vnet.ibm.com" <sebott@linux.vnet.ibm.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>
Subject: dma-mapping: clear harmful GFP_* flags in common code
Date: Mon, 9 Apr 2018 10:52:09 +0000	[thread overview]
Message-ID: <1523271128.5268.32.camel@synopsys.com> (raw)
In-Reply-To: <1522249966.2593.14.camel@synopsys.com>

Hello,

May we have
e89f5b370153 ("dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs")
back-ported to 4.16 kernel as it fixes:

57bf5a8 ("dma-mapping: clear harmful GFP_* flags in common code").

For more info about introduced problem see this thread:
http://lists.infradead.org/pipermail/linux-snps-arc/2018-March/003652.html

-Alexey

WARNING: multiple messages have this Message-ID
From: Alexey Brodkin <Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
To: "stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"sebott-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org"
	<sebott-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	"linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"hch-jcswGhMUV9g@public.gmane.org"
	<hch-jcswGhMUV9g@public.gmane.org>
Subject: dma-mapping: clear harmful GFP_* flags in common code
Date: Mon, 9 Apr 2018 10:52:09 +0000	[thread overview]
Message-ID: <1523271128.5268.32.camel@synopsys.com> (raw)
In-Reply-To: <1522249966.2593.14.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>

Hello,

May we have
e89f5b370153 ("dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs")
back-ported to 4.16 kernel as it fixes:

57bf5a8 ("dma-mapping: clear harmful GFP_* flags in common code").

For more info about introduced problem see this thread:
http://lists.infradead.org/pipermail/linux-snps-arc/2018-March/003652.html

-Alexey

WARNING: multiple messages have this Message-ID
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: dma-mapping: clear harmful GFP_* flags in common code
Date: Mon, 9 Apr 2018 10:52:09 +0000	[thread overview]
Message-ID: <1523271128.5268.32.camel@synopsys.com> (raw)
In-Reply-To: <1522249966.2593.14.camel@synopsys.com>

Hello,

May we have
e89f5b370153 ("dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs")
back-ported to 4.16 kernel as it fixes:

57bf5a8 ("dma-mapping: clear harmful GFP_* flags in common code").

For more info about introduced problem see this thread:
http://lists.infradead.org/pipermail/linux-snps-arc/2018-March/003652.html

-Alexey

  reply	other threads:[~2018-04-09 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 13:35 tip/x86/dma fix for arc and s390 (at least) Christoph Hellwig
2018-03-28 13:35 ` Christoph Hellwig
2018-03-28 13:35 ` [PATCH] dma-mapping: don't clear GFP_ZERO in dma_alloc_attrs Christoph Hellwig
2018-03-28 13:35   ` Christoph Hellwig
2018-03-28 15:12   ` Evgeniy Didin
2018-03-28 15:12     ` Evgeniy Didin
2018-03-28 15:12     ` Evgeniy Didin
2018-04-09 10:52     ` Alexey Brodkin [this message]
2018-04-09 10:52       ` dma-mapping: clear harmful GFP_* flags in common code Alexey Brodkin
2018-04-09 10:52       ` Alexey Brodkin
2018-03-28 15:40   ` [tip:x86/dma] dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs tip-bot for Christoph Hellwig

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=1523271128.5268.32.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=sebott@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=x86@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.