io_uring: comment on kfree(iovec) checks
kfree() handles NULL pointers well, but io_{read,write}() checks it because of performance reasons. Leave a comment there for those who are tempted to patch it. Signed-off-by: Pavel Begunkov <asml.silence@gmail.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:
parent
bb175342aa
commit
f261c16861
@ -3204,6 +3204,7 @@ done:
|
|||||||
kiocb_done(kiocb, ret, cs);
|
kiocb_done(kiocb, ret, cs);
|
||||||
ret = 0;
|
ret = 0;
|
||||||
out_free:
|
out_free:
|
||||||
|
/* it's reportedly faster than delegating the null check to kfree() */
|
||||||
if (iovec)
|
if (iovec)
|
||||||
kfree(iovec);
|
kfree(iovec);
|
||||||
return ret;
|
return ret;
|
||||||
@ -3300,6 +3301,7 @@ copy_iov:
|
|||||||
return -EAGAIN;
|
return -EAGAIN;
|
||||||
}
|
}
|
||||||
out_free:
|
out_free:
|
||||||
|
/* it's reportedly faster than delegating the null check to kfree() */
|
||||||
if (iovec)
|
if (iovec)
|
||||||
kfree(iovec);
|
kfree(iovec);
|
||||||
return ret;
|
return ret;
|
||||||
|
Loading…
Reference in New Issue
Block a user