| commit | 08a2c6019ce873a24377a8b98cad1bff7546ca48 | [log] [tgz] |
|---|---|---|
| author | Paul Sokolovsky <paul.sokolovsky@linaro.org> | Sun Jun 04 14:28:04 2017 +0300 |
| committer | Jukka Rissanen <jukka.rissanen@linux.intel.com> | Mon Jun 05 10:32:28 2017 +0300 |
| tree | 1e0a69a65f4ef9b6cefbb155314826745c23ec88 | |
| parent | 0998cdfba1785765bfbf8ca1836a299943d12722 [diff] |
net: context: Operations on unused context should lead to EBADF. Semantics of ENOENT error as used previously is "named entity not found", whereas for "I/O handle is not valid", there's EBADF. For example, POSIX/SUSV2 doesn't even list ENOENT as a possible error for accept(), connect(), recv(), etc. whereas it lists EBADF, e.g.: http://pubs.opengroup.org/onlinepubs/7908799/xns/connect.html Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>