linux-kernel - Re: PROBLEM: iwlagn kernel 2.6.32.3 ooops

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]

Date:	Wed, 10 Feb 2010 09:21:38 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	reinette chatre <reinette.chatre@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"lkml@...nk-Future.de" <lkml@...nk-Future.de>,
	Linux Kernel-Liste <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: PROBLEM: iwlagn kernel 2.6.32.3 ooops

Hi

On Tue, Feb 09, 2010 at 09:04:52AM -0800, reinette chatre wrote:
> I do not understand your goal here ... as seen in this trace
> pci_alloc_consistent itself already calls dma_alloc_coherent right away.

We can call dma_alloc_coherent with GFP_KERNEL, pci_alloc_consistent is
more or less equal to dma_alloc_coherent with GFP_ATOMIC flag.

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