linux-kernel - Re: [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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150305001954.GA9563@blaptop>
Date:	Thu, 5 Mar 2015 09:20:16 +0900
From:	Minchan Kim <minchan@...nel.org>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
	Jerome Marchand <jmarchan@...hat.com>
Subject: Re: [PATCH 0/2] make automatic device_id generation possible

Hello Sergey,

On Wed, Mar 04, 2015 at 11:16:39PM +0900, Sergey Senozhatsky wrote:
> 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

Thanks for handling my concern quickly and sorry for not sending
active feedback in realtime. Maybe I should turn on CONFIG_PREEMPT
in my brain.

I'm not against but I want to know why we should support
user-defined device id. What usecase do you have in mind?

Could we support automatic id support only at this moment?
Then, if some user complains about that in future, we could turn
on user-defined device id easily and we could know the usecase.

In summary, I want to support only "cat /sys/class/zram-control/zram_add"
unless you have feasible usecase.

What do you think about it?

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

-- 
Kind regards,
Minchan Kim
--
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/