linux-kernel - Re: [PATCH 4/7] tracing: replace a GFP_ATOMIC with GFP

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: <20090615155850.GC19529@elte.hu>
Date:	Mon, 15 Jun 2009 17:58:50 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Li Zefan <lizf@...fujitsu.com>
Subject: Re: [PATCH 4/7] tracing: replace a GFP_ATOMIC with GFP_KERNEL
	allocation


* Steven Rostedt <rostedt@...dmis.org> wrote:

> From: Li Zefan <lizf@...fujitsu.com>
> 
> Atomic allocation is not needed here.
> 
> [ Impact: clean up of memory alloction type ]

Note, the impact line was probably not needed here - and if we add 
one then the correct one would be:

 [ Impact: use less failure-prone (non-atomic) allocations ]

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