You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired by recent changes to compression level parsing by Calvin Owens,
it turns out that we do not do any extra validation for compression
level, thus allowing things like "compress=lzo:invalid" to be accepted
without extra warning or whatever.
Although we accept levels that are beyond the supported algorithm
ranges, accepting completely invalid levels are beyond sanity.
Fix the too loose checks for compression level, by doing proper error
handling of kstrtoint(), so that we will reject not only too large
values (beyond int range) but also completely insane levels like
"lzo:invalid".
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: Qu Wenruo <[email protected]>
0 commit comments