From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f199.google.com (mail-pf0-f199.google.com [209.85.192.199]) by kanga.kvack.org (Postfix) with ESMTP id 245526B0038 for ; Wed, 17 May 2017 09:13:14 -0400 (EDT) Received: by mail-pf0-f199.google.com with SMTP id a66so8776628pfl.6 for ; Wed, 17 May 2017 06:13:14 -0700 (PDT) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com. [45.249.212.188]) by mx.google.com with ESMTPS id d187si2062049pfg.263.2017.05.17.06.13.12 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 17 May 2017 06:13:13 -0700 (PDT) Message-ID: <591C47E5.9010806@huawei.com> Date: Wed, 17 May 2017 20:53:57 +0800 From: zhong jiang MIME-Version: 1.0 Subject: Re: [Qustion] vmalloc area overlap with another allocated vmalloc area References: <591A8814.1010503@huawei.com> In-Reply-To: <591A8814.1010503@huawei.com> Content-Type: text/plain; charset="gb18030" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko , Vlastimil Babka , Joonsoo Kim Cc: Linux Memory Management List , LKML +to linux-mm maintainer for any suggestions Thanks zhongjiang On 2017/5/16 13:03, zhong jiang wrote: > Hi > > I hit the following issue by runing /proc/vmallocinfo. The kernel is 4.1 stable and > 32 bit to be used. after I expand the vamlloc area, the issue is not occur again. > it is related to the overflow. but I do not see any problem so far. > > cat /proc/vmallocinfo > 0xf1580000-0xf1600000 524288 raw_dump_mem_write+0x10c/0x188 phys=8b901000 ioremap > 0xf1638000-0xf163a000 8192 mcss_pou_queue_init+0xa0/0x13c [mcss] phys=fc614000 ioremap > 0xf528e000-0xf5292000 16384 n_tty_open+0x10/0xd0 pages=3 vmalloc > 0xf5000000-0xf9001000 67112960 devm_ioremap+0x38/0x70 phys=40000000 ioremap > 0xfe001000-0xfe002000 4096 iotable_init+0x0/0xc phys=20001000 ioremap > 0xfe200000-0xfe201000 4096 iotable_init+0x0/0xc phys=1a000000 ioremap > 0xff100000-0xff101000 4096 iotable_init+0x0/0xc phys=2000a000 ioremap > > n_tty_open allocate the vmap area is surrounded by the devm_ioremap ioremap by above info. > I do not see also the race in the condition. > > I have no idea to the issue. Anyone has any suggestions will be appreicated. > The related config is attatched. > > Thanks > zhongjiang -- 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 S1754521AbdEQNDa (ORCPT ); Wed, 17 May 2017 09:03:30 -0400 Received: from szxga02-in.huawei.com ([45.249.212.188]:6339 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753224AbdEQND2 (ORCPT ); Wed, 17 May 2017 09:03:28 -0400 Message-ID: <591C47E5.9010806@huawei.com> Date: Wed, 17 May 2017 20:53:57 +0800 From: zhong jiang User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Michal Hocko , Vlastimil Babka , Joonsoo Kim CC: Linux Memory Management List , LKML Subject: Re: [Qustion] vmalloc area overlap with another allocated vmalloc area References: <591A8814.1010503@huawei.com> In-Reply-To: <591A8814.1010503@huawei.com> Content-Type: text/plain; charset="gb18030" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.29.68] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.591C4899.0045,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 438f94fed0fc87fd1d0ac97022d6e81c Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +to linux-mm maintainer for any suggestions Thanks zhongjiang On 2017/5/16 13:03, zhong jiang wrote: > Hi > > I hit the following issue by runing /proc/vmallocinfo. The kernel is 4.1 stable and > 32 bit to be used. after I expand the vamlloc area, the issue is not occur again. > it is related to the overflow. but I do not see any problem so far. > > cat /proc/vmallocinfo > 0xf1580000-0xf1600000 524288 raw_dump_mem_write+0x10c/0x188 phys=8b901000 ioremap > 0xf1638000-0xf163a000 8192 mcss_pou_queue_init+0xa0/0x13c [mcss] phys=fc614000 ioremap > 0xf528e000-0xf5292000 16384 n_tty_open+0x10/0xd0 pages=3 vmalloc > 0xf5000000-0xf9001000 67112960 devm_ioremap+0x38/0x70 phys=40000000 ioremap > 0xfe001000-0xfe002000 4096 iotable_init+0x0/0xc phys=20001000 ioremap > 0xfe200000-0xfe201000 4096 iotable_init+0x0/0xc phys=1a000000 ioremap > 0xff100000-0xff101000 4096 iotable_init+0x0/0xc phys=2000a000 ioremap > > n_tty_open allocate the vmap area is surrounded by the devm_ioremap ioremap by above info. > I do not see also the race in the condition. > > I have no idea to the issue. Anyone has any suggestions will be appreicated. > The related config is attatched. > > Thanks > zhongjiang