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
| ||
|
Date: Fri, 22 May 2015 17:56:12 +0900 From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> To: Marcin Jabrzyk <m.jabrzyk@...sung.com> Cc: minchan@...nel.org, ngupta@...are.org, sergey.senozhatsky.work@...il.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org, kyungmin.park@...sung.com Subject: Re: [PATCH] zram: check compressor name before setting it On (05/22/15 10:31), Marcin Jabrzyk wrote: > Zram sysfs interface was not making any check of > proper compressor name when setting it. > Any name is accepted, but further tries of device > creation would end up with not very meaningfull error. > eg. > > echo lz0 > comp_algorithm > echo 200M > disksize > echo: write error: Invalid argument > no. zram already complains about failed comp backend creation. it's in dmesg (or syslog, etc.): "zram: Cannot initialise %s compressing backend" second, there is not much value in exposing zcomp internals, especially when the result is just another line in dmesg output. -ss -- 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/
Powered by blists - more mailing lists