linux-kernel - [PATCH v2 0/2] zram: cleanup stream's ->private allocation code

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

Message-Id: <1448973518-21745-1-git-send-email-sergey.senozhatsky@gmail.com>
Date:	Tue,  1 Dec 2015 21:38:36 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: [PATCH v2 0/2] zram: cleanup stream's ->private allocation code

Hello,
        Two patches that 'cleanup' compression streams allocation.
Patch #1 consolidates GFP flags used for stream's ->private
allocation in underlying compression backends.

Patch #2 drops GFP_ZERO flag from ->private allocation.


This patch set depends on the patch set published here
http://marc.info/?l=linux-kernel&m=144897349318883


V2:
-- do not use __GFP_NOMEMALLOC for zcomp private allocation.


Minchan Kim (1):
  zram: pass gfp from zcomp frontend to backend

Sergey Senozhatsky (1):
  zram/zcomp: do not zero out zcomp private pages

 drivers/block/zram/zcomp.c     | 24 ++++++++++++++++--------
 drivers/block/zram/zcomp.h     |  2 +-
 drivers/block/zram/zcomp_lz4.c | 16 +++-------------
 drivers/block/zram/zcomp_lzo.c | 16 +++-------------
 4 files changed, 23 insertions(+), 35 deletions(-)

-- 
2.6.2

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