linux-kernel - Re: [lkp] [block] 86ecb9456ac:

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAF1ivSaRQcKvg+ogu+TfV-tw_zZ4pG1JtPkbgrCcJf2R58UY5Q@mail.gmail.com>
Date:	Tue, 14 Jul 2015 10:31:20 -0700
From:	Ming Lin <mlin@...nel.org>
To:	Huang Ying <ying.huang@...el.com>
Cc:	Kent Overstreet <kent.overstreet@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, LKP ML <lkp@...org>
Subject: Re: [lkp] [block] 86ecb9456ac:

On Tue, Jul 14, 2015 at 6:26 AM, Huang Ying <ying.huang@...el.com> wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mlin/linux.git block-generic-req
> commit 86ecb9456ac74ba3996d05ca1b09a7756a31bfd7 ("block: make generic_make_request handle arbitrarily sized bios")
>
> We found the following new message in kernel log, do you increase vmalloc usage in your patch?
>
> [    6.939422] vmap allocation for size 16384 failed: use vmalloc=<size> to increase size.

[    6.939422] vmap allocation for size 16384 failed: use
vmalloc=<size> to increase size.
[    6.955278] lguest: could not map switcher pages high

This actually comes from lguest.

Several weeks ago I tried lguest on qemu-kvm-i386 and saw similar problem.
I didn't debug it further, but it's OK if disable CONFIG_SMP.

I just double-checked it with v4.2-rc1(without this patchset)
CONFIG_SMP: see the vmalloc error
!CONFIG_SMP: no problem

Could you confirm?

BTW, it seams "qemu-kvm-i386 guest" as "lguest host" doesn't work.
Need to run lguest on bare metal.

Thanks.

>
>
> Thanks,
> Ying Huang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/