All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joonsoo Kim <js1304@gmail.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Laura Abbott" <labbott@redhat.com>,
	"Michal Hocko" <mhocko@kernel.org>,
	"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Laura Abbott" <lauraa@codeaurora.org>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Mel Gorman" <mgorman@techsingularity.net>,
	"Michal Nazarewicz" <mina86@mina86.com>,
	"Minchan Kim" <minchan@kernel.org>,
	"Rik van Riel" <riel@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Will Deacon" <will.deacon@arm.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"
Date: Tue, 22 May 2018 17:02:57 -0700	[thread overview]
Message-ID: <20180522170257.ae5387d8717e81def908a53b@linux-foundation.org> (raw)
In-Reply-To: <20180521061631.GA26882@js1304-desktop>

On Mon, 21 May 2018 15:16:33 +0900 Joonsoo Kim <js1304@gmail.com> wrote:

> > (gdb) list *(dma_direct_alloc+0x22f)
> > 0x573fbf is in dma_direct_alloc (../lib/dma-direct.c:104).
> > 94	
> > 95		if (!page)
> > 96			return NULL;
> > 97		ret = page_address(page);
> > 98		if (force_dma_unencrypted()) {
> > 99			set_memory_decrypted((unsigned long)ret, 1 << page_order);
> > 100			*dma_handle = __phys_to_dma(dev, page_to_phys(page));
> > 101		} else {
> > 102			*dma_handle = phys_to_dma(dev, page_to_phys(page));
> > 103		}
> > 104		memset(ret, 0, size);
> > 105		return ret;
> > 106	}
> > 
> 
> Okay. I find the reason about this error.

It's getting rather late and we don't seem to have a final set of fixes
yet.  Perhaps the best approach here is to revert and try again for
4.18?

  reply	other threads:[~2018-05-23  0:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 12:59 [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE" Ville Syrjala
2018-05-17 12:59 ` Ville Syrjala
2018-05-17 13:15 ` Vlastimil Babka
2018-05-17 13:15   ` Vlastimil Babka
2018-05-17 13:21 ` Michal Hocko
2018-05-17 13:21   ` Michal Hocko
2018-05-17 13:36   ` Ville Syrjälä
2018-05-17 13:36     ` Ville Syrjälä
2018-05-17 13:50     ` Vlastimil Babka
2018-05-17 13:50       ` Vlastimil Babka
2018-05-17 13:58     ` Ville Syrjälä
2018-05-17 13:58       ` Ville Syrjälä
2018-05-17 14:11       ` Ville Syrjälä
2018-05-17 14:11         ` Ville Syrjälä
2018-05-17 16:49       ` Michal Hocko
2018-05-17 16:49         ` Michal Hocko
2018-05-17 17:08         ` Michal Hocko
2018-05-17 17:08           ` Michal Hocko
2018-05-17 17:53           ` Laura Abbott
2018-05-17 17:53             ` Laura Abbott
2018-05-18  4:01             ` Joonsoo Kim
2018-05-18  4:01               ` Joonsoo Kim
2018-05-18 17:42               ` Laura Abbott
2018-05-18 17:42                 ` Laura Abbott
2018-05-19 14:46               ` Ville Syrjälä
2018-05-19 14:46                 ` Ville Syrjälä
2018-05-21  6:16                 ` Joonsoo Kim
2018-05-21  6:16                   ` Joonsoo Kim
2018-05-23  0:02                   ` Andrew Morton [this message]
2018-05-23  0:09                     ` Joonsoo Kim
2018-05-17 17:13         ` Ville Syrjälä
2018-05-17 17:13           ` Ville Syrjälä
2018-05-17 17:21           ` Michal Hocko
2018-05-17 17:21             ` Michal Hocko
2018-05-17 19:55           ` Ville Syrjälä
2018-05-17 19:55             ` Ville Syrjälä
2018-05-23  1:18 js1304
2018-05-23  1:18 ` js1304
2018-05-23 18:54 ` Laura Abbott
2018-05-23 18:54   ` Laura Abbott
2018-05-24 11:28 ` Michal Hocko
2018-05-24 11:28   ` Michal Hocko

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=20180522170257.ae5387d8717e81def908a53b@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=js1304@gmail.com \
    --cc=labbott@redhat.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=mina86@mina86.com \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=ville.syrjala@linux.intel.com \
    --cc=will.deacon@arm.com \
    /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.