linux-kernel - Re: [patch] block: use caller's GFP flags instead of 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: <4F6C3B1F.9090703@kernel.dk>
Date:	Fri, 23 Mar 2012 09:58:07 +0100
From:	Jens Axboe <axboe@...nel.dk>
To:	Dan Carpenter <dan.carpenter@...cle.com>
CC:	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [patch] block: use caller's GFP flags instead of GFP_KERNEL

On 03/23/2012 09:36 AM, Dan Carpenter wrote:
> We should use the GFP flags that the caller specified instead of picking
> our own.  All the callers specify GFP_KERNEL so this doesn't make a
> difference to how the kernel runs, it's just a cleanup.

Thanks Dan, applied to for-3.4/core

-- 
Jens Axboe

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