From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Hellstrom Subject: Re: page allocator bug in 3.16? Date: Fri, 26 Sep 2014 09:15:57 +0200 Message-ID: <542512AD.9070304@vmware.com> References: <54246506.50401@hurleysoftware.com> <20140925143555.1f276007@as> <5424AAD0.9010708@hurleysoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by gabe.freedesktop.org (Postfix) with ESMTP id C1E206E089 for ; Fri, 26 Sep 2014 00:16:21 -0700 (PDT) In-Reply-To: <5424AAD0.9010708@hurleysoftware.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Peter Hurley Cc: Rik van Riel , Linus Torvalds , Hugh Dickens , Chuck Ebbert , "dri-devel@lists.freedesktop.org" , Linux kernel , linux-mm , Mel Gorman , Andrew Morton , Shaohua Li , Ingo Molnar List-Id: dri-devel@lists.freedesktop.org On 09/26/2014 01:52 AM, Peter Hurley wrote: > On 09/25/2014 03:35 PM, Chuck Ebbert wrote: >> There are six ttm patches queued for 3.16.4: >> >> drm-ttm-choose-a-pool-to-shrink-correctly-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-handling-of-ttm_pl_flag_topdown-v2.patch >> drm-ttm-fix-possible-division-by-0-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-possible-stack-overflow-by-recursive-shrinker-calls.patch >> drm-ttm-pass-gfp-flags-in-order-to-avoid-deadlock.patch >> drm-ttm-use-mutex_trylock-to-avoid-deadlock-inside-shrinker-functions.patch > Thanks for info, Chuck. > > Unfortunately, none of these fix TTM dma allocation doing CMA dma allocation, > which is the root problem. > > Regards, > Peter Hurley The problem is not really in TTM but in CMA, There was a guy offering to fix this in the CMA code but I guess he didn't probably because he didn't receive any feedback. /Thomas From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by kanga.kvack.org (Postfix) with ESMTP id 108B96B0038 for ; Fri, 26 Sep 2014 03:16:24 -0400 (EDT) Received: by mail-pd0-f169.google.com with SMTP id p10so437220pdj.14 for ; Fri, 26 Sep 2014 00:16:23 -0700 (PDT) Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com. [208.91.2.12]) by mx.google.com with ESMTPS id pl6si7703725pdb.111.2014.09.26.00.16.21 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 26 Sep 2014 00:16:23 -0700 (PDT) Message-ID: <542512AD.9070304@vmware.com> Date: Fri, 26 Sep 2014 09:15:57 +0200 From: Thomas Hellstrom MIME-Version: 1.0 Subject: Re: page allocator bug in 3.16? References: <54246506.50401@hurleysoftware.com> <20140925143555.1f276007@as> <5424AAD0.9010708@hurleysoftware.com> In-Reply-To: <5424AAD0.9010708@hurleysoftware.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Peter Hurley Cc: Chuck Ebbert , Mel Gorman , Shaohua Li , Rik van Riel , Maarten Lankhorst , Andrew Morton , Linus Torvalds , Linux kernel , linux-mm , Ingo Molnar , Hugh Dickens , "dri-devel@lists.freedesktop.org" On 09/26/2014 01:52 AM, Peter Hurley wrote: > On 09/25/2014 03:35 PM, Chuck Ebbert wrote: >> There are six ttm patches queued for 3.16.4: >> >> drm-ttm-choose-a-pool-to-shrink-correctly-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-handling-of-ttm_pl_flag_topdown-v2.patch >> drm-ttm-fix-possible-division-by-0-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-possible-stack-overflow-by-recursive-shrinker-calls.patch >> drm-ttm-pass-gfp-flags-in-order-to-avoid-deadlock.patch >> drm-ttm-use-mutex_trylock-to-avoid-deadlock-inside-shrinker-functions.patch > Thanks for info, Chuck. > > Unfortunately, none of these fix TTM dma allocation doing CMA dma allocation, > which is the root problem. > > Regards, > Peter Hurley The problem is not really in TTM but in CMA, There was a guy offering to fix this in the CMA code but I guess he didn't probably because he didn't receive any feedback. /Thomas -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753809AbaIZHQW (ORCPT ); Fri, 26 Sep 2014 03:16:22 -0400 Received: from smtp-outbound-1.vmware.com ([208.91.2.12]:39392 "EHLO smtp-outbound-1.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753029AbaIZHQV (ORCPT ); Fri, 26 Sep 2014 03:16:21 -0400 Message-ID: <542512AD.9070304@vmware.com> Date: Fri, 26 Sep 2014 09:15:57 +0200 From: Thomas Hellstrom User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Peter Hurley CC: Chuck Ebbert , Mel Gorman , Shaohua Li , Rik van Riel , "Maarten Lankhorst" , Andrew Morton , Linus Torvalds , Linux kernel , linux-mm , Ingo Molnar , Hugh Dickens , "dri-devel@lists.freedesktop.org" Subject: Re: page allocator bug in 3.16? References: <54246506.50401@hurleysoftware.com> <20140925143555.1f276007@as> <5424AAD0.9010708@hurleysoftware.com> In-Reply-To: <5424AAD0.9010708@hurleysoftware.com> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.160.246] X-ClientProxiedBy: EX13-CAS-013.vmware.com (10.113.191.65) To EX13-MBX-024.vmware.com (10.113.191.44) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/26/2014 01:52 AM, Peter Hurley wrote: > On 09/25/2014 03:35 PM, Chuck Ebbert wrote: >> There are six ttm patches queued for 3.16.4: >> >> drm-ttm-choose-a-pool-to-shrink-correctly-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-handling-of-ttm_pl_flag_topdown-v2.patch >> drm-ttm-fix-possible-division-by-0-in-ttm_dma_pool_shrink_scan.patch >> drm-ttm-fix-possible-stack-overflow-by-recursive-shrinker-calls.patch >> drm-ttm-pass-gfp-flags-in-order-to-avoid-deadlock.patch >> drm-ttm-use-mutex_trylock-to-avoid-deadlock-inside-shrinker-functions.patch > Thanks for info, Chuck. > > Unfortunately, none of these fix TTM dma allocation doing CMA dma allocation, > which is the root problem. > > Regards, > Peter Hurley The problem is not really in TTM but in CMA, There was a guy offering to fix this in the CMA code but I guess he didn't probably because he didn't receive any feedback. /Thomas