Searched hist:"21226 abb4e9f14d88238964d89b279e461ddc30c" (Results 1 – 7 of 7) sorted by relevance
/openbmc/linux/include/net/ |
H A D | udplite.h | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/net/ipv4/ |
H A D | ping.c | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | raw.c | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | ip_output.c | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | tcp_input.c | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/net/ipv6/ |
H A D | raw.c | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/include/linux/ |
H A D | skbuff.h | diff 21226abb4e9f14d88238964d89b279e461ddc30c Fri Nov 28 14:48:29 CST 2014 Al Viro <viro@zeniv.linux.org.uk> net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
That takes care of the majority of ->sendmsg() instances - most of them via memcpy_to_msg() or assorted getfrag() callbacks. One place where we still keep memcpy_fromiovecend() is tipc - there we potentially read the same data over and over; separate patch, that...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|