From: Michal Nazarewicz <mina86@mina86.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated
Date: Fri, 24 Oct 2014 16:34:46 +0000 [thread overview]
Message-ID: <xa1tfved2zq1.fsf@mina86.com> (raw)
In-Reply-To: <1463193.4qGZjcvNod@avalon>
> On Thursday 23 October 2014 18:53:36 Michal Nazarewicz wrote:
>> As a matter of fact, this is present in kernels earlier than 3.17 but in
>> the 3.17 the code has been moved from drivers/base/dma-contiguous.c to
>> mm/cma.c so this might require separate stable patch.
On Fri, Oct 24 2014, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> That could be done, but I'm not sure if it's really worth it. The bug only
> occurs when the CMA zone activation fails. I've ran into that case due to a
> bug introduced in v3.18-rc1, but this shouldn't be the case for older kernel
> versions.
Fair enough.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
WARNING: multiple messages have this Message-ID (diff)
From: mina86@mina86.com (Michal Nazarewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated
Date: Fri, 24 Oct 2014 18:34:46 +0200 [thread overview]
Message-ID: <xa1tfved2zq1.fsf@mina86.com> (raw)
In-Reply-To: <1463193.4qGZjcvNod@avalon>
> On Thursday 23 October 2014 18:53:36 Michal Nazarewicz wrote:
>> As a matter of fact, this is present in kernels earlier than 3.17 but in
>> the 3.17 the code has been moved from drivers/base/dma-contiguous.c to
>> mm/cma.c so this might require separate stable patch.
On Fri, Oct 24 2014, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> That could be done, but I'm not sure if it's really worth it. The bug only
> occurs when the CMA zone activation fails. I've ran into that case due to a
> bug introduced in v3.18-rc1, but this shouldn't be the case for older kernel
> versions.
Fair enough.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Micha? ?mina86? Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
WARNING: multiple messages have this Message-ID (diff)
From: Michal Nazarewicz <mina86@mina86.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated
Date: Fri, 24 Oct 2014 18:34:46 +0200 [thread overview]
Message-ID: <xa1tfved2zq1.fsf@mina86.com> (raw)
In-Reply-To: <1463193.4qGZjcvNod@avalon>
> On Thursday 23 October 2014 18:53:36 Michal Nazarewicz wrote:
>> As a matter of fact, this is present in kernels earlier than 3.17 but in
>> the 3.17 the code has been moved from drivers/base/dma-contiguous.c to
>> mm/cma.c so this might require separate stable patch.
On Fri, Oct 24 2014, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> That could be done, but I'm not sure if it's really worth it. The bug only
> occurs when the CMA zone activation fails. I've ran into that case due to a
> bug introduced in v3.18-rc1, but this shouldn't be the case for older kernel
> versions.
Fair enough.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Nazarewicz <mina86@mina86.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated
Date: Fri, 24 Oct 2014 18:34:46 +0200 [thread overview]
Message-ID: <xa1tfved2zq1.fsf@mina86.com> (raw)
In-Reply-To: <1463193.4qGZjcvNod@avalon>
> On Thursday 23 October 2014 18:53:36 Michal Nazarewicz wrote:
>> As a matter of fact, this is present in kernels earlier than 3.17 but in
>> the 3.17 the code has been moved from drivers/base/dma-contiguous.c to
>> mm/cma.c so this might require separate stable patch.
On Fri, Oct 24 2014, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> That could be done, but I'm not sure if it's really worth it. The bug only
> occurs when the CMA zone activation fails. I've ran into that case due to a
> bug introduced in v3.18-rc1, but this shouldn't be the case for older kernel
> versions.
Fair enough.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
next prev parent reply other threads:[~2014-10-24 16:34 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 14:33 [PATCH 0/4] Low/high memory CMA reservation fixes Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 16:34 ` Michal Nazarewicz [this message]
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-23 14:33 ` [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 3/4] mm: cma: Ensure that reservations never cross the low/high mem boundary Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 4/4] mm: cma: Use %pa to print physical addresses Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
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=xa1tfved2zq1.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=linux-arm-kernel@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 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.