linux-kernel - [PATCH 0/2] make automatic device

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: <1425478601-19141-1-git-send-email-sergey.senozhatsky@gmail.com>
Date:	Wed,  4 Mar 2015 23:16:39 +0900
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Minchan Kim <minchan@...nel.org>
Cc:	Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: [PATCH 0/2] make automatic device_id generation possible

Hello,

Make zram-contol/zram_add interface easier to use. Extend it to support
read and write operations.

Write operation remains the same:

	echo X > /sys/class/zram-control/zram_add

will add /dev/zramX (or return error).


Read operation is treated as 'pick up available device_id, add new
device and return device_id'.

Example:
	 cat /sys/class/zram-control/zram_add
	2
	 cat /sys/class/zram-control/zram_add
	3

Sergey Senozhatsky (2):
  zram: return zram device_id value from zram_add()
  zram: introduce automatic device_id generation

 Documentation/ABI/testing/sysfs-class-zram |  7 ++++--
 Documentation/blockdev/zram.txt            | 10 ++++++++
 drivers/block/zram/zram_drv.c              | 37 ++++++++++++++++++++++++++----
 3 files changed, 47 insertions(+), 7 deletions(-)

-- 
2.3.1.167.g7f4ba4b

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