Re: [PATCH v3] packet: fix second argument of sock_tx_timestamp()

2016-07-19 Thread David Miller
From: Yoshihiro Shimoda Date: Tue, 19 Jul 2016 14:40:51 +0900 > This patch fixes an issue that a syscall (e.g. sendto syscall) cannot > work correctly. Since the sendto syscall doesn't have msg_control buffer, > the sock_tx_timestamp() in packet_snd() cannot

Re: [PATCH v3] packet: fix second argument of sock_tx_timestamp()

2016-07-19 Thread Willem de Bruijn
On Tue, Jul 19, 2016 at 8:34 AM, Soheil Hassas Yeganeh wrote: > On Tue, Jul 19, 2016 at 1:40 AM, Yoshihiro Shimoda > wrote: >> This patch fixes an issue that a syscall (e.g. sendto syscall) cannot >> work correctly. Since the sendto syscall

Re: [PATCH v3] packet: fix second argument of sock_tx_timestamp()

2016-07-19 Thread Soheil Hassas Yeganeh
On Tue, Jul 19, 2016 at 1:40 AM, Yoshihiro Shimoda wrote: > This patch fixes an issue that a syscall (e.g. sendto syscall) cannot > work correctly. Since the sendto syscall doesn't have msg_control buffer, > the sock_tx_timestamp() in packet_snd() cannot work

[PATCH v3] packet: fix second argument of sock_tx_timestamp()

2016-07-18 Thread Yoshihiro Shimoda
This patch fixes an issue that a syscall (e.g. sendto syscall) cannot work correctly. Since the sendto syscall doesn't have msg_control buffer, the sock_tx_timestamp() in packet_snd() cannot work correctly because the socks.tsflags is set to 0. So, this patch sets the socks.tsflags to