7d985ed1dc
[I would really like an ACK on that one from dhowells; it appears to be quite straightforward, but...] MSG_PEEK isn't passed to ->recvmsg() via msg->msg_flags; as the matter of fact, neither the kernel users of rxrpc, nor the syscalls ever set that bit in there. It gets passed via flags; in fact, another such check in the same function is done correctly - as flags & MSG_PEEK. It had been that way (effectively disabled) for 8 years, though, so the patch needs beating up - that case had never been tested. If it is correct, it's -stable fodder. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
---|---|---|
.. | ||
af_rxrpc.c | ||
ar-accept.c | ||
ar-ack.c | ||
ar-call.c | ||
ar-connection.c | ||
ar-connevent.c | ||
ar-error.c | ||
ar-input.c | ||
ar-internal.h | ||
ar-key.c | ||
ar-local.c | ||
ar-output.c | ||
ar-peer.c | ||
ar-proc.c | ||
ar-recvmsg.c | ||
ar-security.c | ||
ar-skbuff.c | ||
ar-transport.c | ||
Kconfig | ||
Makefile | ||
rxkad.c | ||
sysctl.c |