Hi,
On 22/05/15 10:56, Sergey Senozhatsky wrote:
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"
OK, now I see that. Sorry for the noise.
second, there is not much value in exposing zcomp internals,
especially when the result is just another line in dmesg output.
From the other hand, the only valid values that can be written are
in 'comp_algorithm'.
So when writing other one, returning -EINVAL seems to be reasonable.
The user would get immediately information that he can't do that,
now the information can be very deferred in time.
I'm not for exposing more internals, but getting -EINVAL would be nice I
think.
-ss
Best regards,
Marcin Jabrzyk
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>