From: Mel Gorman <mgorman@suse.de>
To: Tony Prisk <linux@prisktech.co.nz>
Cc: linux-mm@kvack.org,
Arm Kernel Mailing List <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: dma_alloc_coherent fails in framebuffer
Date: Tue, 16 Oct 2012 08:58:35 +0100 [thread overview]
Message-ID: <20121016075835.GF29125@suse.de> (raw)
In-Reply-To: <1350370207.26424.13.camel@gitbox>
On Tue, Oct 16, 2012 at 07:50:07PM +1300, Tony Prisk wrote:
> > > > Why it caused a problem on that particular commit I don't know - but it
> > > > was reproducible by adding/removing it.
> > > >
> >
> > I finally found the link to this patch which caused the problem - and
> > may still be the cause of my problems :)
> >
Blast, thanks. This was already identified as being a problem and "fixed"
in https://lkml.org/lkml/2012/10/5/164 but I missed that the fix did not
get picked up before RC1 after all the patches got collapsed together. I'm
very sorry about that, I should have spotted that it didn't make it through.
> Any suggestions on how to fix this?
>
Can you test this to be sure and if it's fine I'll push it to Andrew.
---8<---
mm: compaction: Correct the strict_isolated check for CMA
Thierry reported that the "iron out" patch for isolate_freepages_block()
had problems due to the strict check being too strict with "mm: compaction:
Iron out isolate_freepages_block() and isolate_freepages_range() -fix1".
It's possible that more pages than necessary are isolated but the check
still fails and I missed that this fix was not picked up before RC1. This
has also been identified in RC1 by Tony Prisk and should be addressed by
the following patch.
Signed-off-by: Mel Gorman <mgorman@suse.de>
---
compaction.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/compaction.c b/mm/compaction.c
index 2c4ce17..9eef558 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -346,7 +346,7 @@ static unsigned long isolate_freepages_block(struct compact_control *cc,
* pages requested were isolated. If there were any failures, 0 is
* returned and CMA will fail.
*/
- if (strict && nr_strict_required != total_isolated)
+ if (strict && nr_strict_required > total_isolated)
total_isolated = 0;
if (locked)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-10-16 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350192523.10946.4.camel@gitbox>
2012-10-14 20:34 ` dma_alloc_coherent fails in framebuffer Tony Prisk
2012-10-14 22:26 ` Tony Prisk
2012-10-15 6:42 ` Tomasz Figa
2012-10-15 8:03 ` Tony Prisk
2012-10-15 13:35 ` Marek Szyprowski
2012-10-15 9:45 ` Mel Gorman
2012-10-15 18:28 ` Tony Prisk
2012-10-16 2:17 ` Bob Liu
2012-10-16 5:02 ` Tony Prisk
2012-10-16 5:54 ` Tony Prisk
2012-10-16 6:50 ` Tony Prisk
2012-10-16 7:58 ` Mel Gorman [this message]
2012-10-16 8:13 ` Tony Prisk
2012-10-16 14:41 ` James Bottomley
2012-10-17 2:26 ` Bob Liu
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=20121016075835.GF29125@suse.de \
--to=mgorman@suse.de \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux@prisktech.co.nz \
/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).