linux-kernel - Re: [rfc 2/2] x86, bts: use physically non-contiguous trace buffer

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1240829616.7620.7.camel@twins>
Date:	Mon, 27 Apr 2009 12:53:36 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Markus Metzger <markus.t.metzger@...el.com>,
	markus.t.metzger@...il.com, roland@...hat.com,
	eranian@...glemail.com, oleg@...hat.com, juan.villacis@...el.com,
	ak@...ux.jf.intel.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, hpa@...or.com
Subject: Re: [rfc 2/2] x86, bts: use physically non-contiguous trace buffer

On Fri, 2009-04-24 at 10:31 +0200, Ingo Molnar wrote:
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> 

> > The patch looks like a regression to me.  vmalloc memory is slower 
> > to allocate, slower to free, slower to access and can exhaust or 
> > fragment the vmalloc arena.  Confused.
> 
> Performance does not matter here (this is really a slowpath), but 
> fragmentation does matter, especially on 32-bit systems.
> 
> I'd not uglify the code via vmap() - and vmap has the same 
> fundamental address space limitations on 32-bit as vmalloc().
> 
> The existing kmalloc() is fine. We do larger than PAGE_SIZE 
> allocations elsewhere too (the kernel stack for example), and this 
> is a debug facility, so failing the allocation is not a big problem 
> even if it happens.

Nobody has yet told what the typical size of these allocations are. If
they're large enough to account in pages, one should arguable use the
page allocator not kmalloc. Also, any >3 order allocation (>32kb) are
very likely to fail. Having this ptrace interface work in the (unloaded)
development environment but not in a (loaded) production environment
will render it basically useless IMHO.

Having a regular high order allocation with vmalloc/vmap fallback is
quite normal, esp. if one wants to promote the use of this facility as
usable.

So, no, I very strongly disagree that the existing kmalloc is fine.

PS. I get shitloads of order-4 alloc failures from GEM after a few days
of uptime on my laptop.

--
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/