On Fri, Feb 28, 2014 at 10:54:24PM -0500, Sasha Levin wrote:
> We would never check the return value of __radix_tree_create() on insertion
> which would cause us to return -EEXIST on all cases of failure, even when
> such failure would be running out of memory, for example.
>
> This would trigger
On Fri, Feb 28, 2014 at 10:54:24PM -0500, Sasha Levin wrote:
We would never check the return value of __radix_tree_create() on insertion
which would cause us to return -EEXIST on all cases of failure, even when
such failure would be running out of memory, for example.
This would trigger
We would never check the return value of __radix_tree_create() on insertion
which would cause us to return -EEXIST on all cases of failure, even when
such failure would be running out of memory, for example.
This would trigger errors in various code that assumed that -EEXIST is
a critical
We would never check the return value of __radix_tree_create() on insertion
which would cause us to return -EEXIST on all cases of failure, even when
such failure would be running out of memory, for example.
This would trigger errors in various code that assumed that -EEXIST is
a critical
4 matches
Mail list logo