On 05/12/2014 01:11 PM, David Miller wrote:
So it makes sense to return errors for send() syscall.
Signed-off-by: Xufeng Zhang<xufeng.zh...@windriver.com>
I disagree.
If pfkey_error() is successful, the error will be reported in the AF_KEY
message that is broadcast, there is no reason for sendmsg to return an
error. The message was sucessfully sent, there was no problem with it's
passage into the AF_KEY layer.
Like netlink, operational responses come in packets, not error codes.
However, if pfkey_error() fails, we must do pass back the original
error code because it's a last ditch effort to prevent information
from being lost.
That's why 'err' must be preserved when pfkey_error() returns zero.
I know what you mean, but isn't the kernel API aimed to facilitate the
implementation of user space?
Since send the message to the kernel and receive the error report message
are asynchronous, I don't think it's easy to recover from the EINTR error
by parsing the error report message.
Thanks,
Xufeng
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
