From: Michal Hocko <mhocko@kernel.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Qustion] vmalloc area overlap with another allocated vmalloc area
Date: Wed, 17 May 2017 15:44:12 +0200 [thread overview]
Message-ID: <20170517134412.GL18247@dhcp22.suse.cz> (raw)
In-Reply-To: <591C47E5.9010806@huawei.com>
On Wed 17-05-17 20:53:57, zhong jiang wrote:
> +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.
Is this a clean 4.1 stable kernel without any additional patches on top?
Are you able to reproduce this? How? Does the same problem happen with
the current Linus tree?
> > 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
>
--
Michal Hocko
SUSE Labs
--
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:[~2017-05-17 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 5:03 [Qustion] vmalloc area overlap with another allocated vmalloc area zhong jiang
2017-05-17 12:53 ` zhong jiang
2017-05-17 13:44 ` Michal Hocko [this message]
2017-05-17 14:23 ` zhong jiang
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=20170517134412.GL18247@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=zhongjiang@huawei.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 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).