Hello. Thank you for your comment.
David Miller wrote: > I don't think it's such a hot idea to return errors if the > wait_on_sync_kiocb() has returned success. My patch may return errors for non-wait_on_sync_kiocb() case too. Are you saying only wait_on_sync_kiocb() case is bad? If so, could you please explain me why? The location I inserted a hook is "after aio event finished". Both "struct kiocb" and "struct sock_iocb" are no longer in use. So, I think this location can safely return errors. If you are saying "don't return error after receiving data", I'll explain you why I need hooks after receiving data. What I want to do is to implement a kind of anti-virus software's personal firewall feature. It drops messages from unwanted IP address/ports. (To be exact, it doesn't drop, it just tells userland process not to use received messages by returning errors.) security_socket_recvmsg() is called before retrieving a message. I want a hook that is called after retrieving a message so that I can use IP address and port number for judgement. I also want to allow users judge interactively using a popup dialog. To judge interactively, the hook has to be block-able. If non-interactive, iptables is the appropriate location for filtering. This is why I want to insert security_socket_post_recvmsg() hook here. Regards. - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
