linux-kernel - Re: [PATCH 1/2] zram: pass gfp from zcomp frontend to backend

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:	Mon, 30 Nov 2015 16:10:04 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc:	Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [PATCH 1/2] zram: pass gfp from zcomp frontend to backend

On Fri, 27 Nov 2015 13:23:13 +0900 Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:

> From: Minchan Kim <minchan@...nel.org>
> 
> Each zcomp backend uses own gfp flag but it's pointless
> because the context they could be called is driven by upper
> layer(ie, zcomp frontend). As well, zcomp frondend could
> call them in different context. One context(ie, zram init part)
> is it should be better to make sure successful allocation
> other context(ie, further stream allocation part for accelarating
> I/O speed) is just optional so let's pass gfp down from driver
> (ie, zcomp frontend) like normal MM convention.
> 
> [sergey: add missing __vmalloc zero and highmem gfps]
> Signed-off-by: Minchan Kim <minchan@...nel.org>
> Acked-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>

I changed this to signed-off-by:you.  Documentation/SubmittingPatches
section 11 explains why ;)

(Hm, rule (c) is recursive.  Nice!)
--
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/