From: Soheil Hassas Yeganeh <soheil@google.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: David Miller <davem@davemloft.net>,
daniel@iogearbox.net, Willem de Bruijn <willemb@google.com>,
ast@plumgrid.com, tklauser@distanz.ch,
fruggeri@aristanetworks.com, netdev <netdev@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] packet: fix second argument of sock_tx_timestamp()
Date: Tue, 19 Jul 2016 08:34:20 -0400 [thread overview]
Message-ID: <CACSApvYj5X166euM2Qy+ubvLYdfYg65itMYiVeTf5SUuiA+gog@mail.gmail.com> (raw)
In-Reply-To: <1468906851-8424-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
On Tue, Jul 19, 2016 at 1:40 AM, Yoshihiro Shimoda
<yoshihiro.shimoda.uh@renesas.com> 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 correctly because
> the socks.tsflags is set to 0.
> So, this patch sets the socks.tsflags to sk->sk_tsflags as default.
>
> Fixes: c14ac9451c34 ("sock: enable timestamping using control messages")
> Cc: <stable@vger.kernel.org>
> Reported-by: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
> Reported-by: Keita Kobayashi <keita.kobayashi.ym@renesas.com>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
> ---
> Changes from v2:
> - Fix build error...
>
> Changes from v1:
> - Set socks.tsflags to sk->sk_tsflags as default instead of a condition.
> - Fix other socks.tsflags values in the af_packet.c.
> - Revise the commit log.
>
> About v1 (as RFC):
> - http://thread.gmane.org/gmane.linux.kernel.renesas-soc/5646
>
> net/packet/af_packet.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
> index 9f0983f..53e87ce 100644
> --- a/net/packet/af_packet.c
> +++ b/net/packet/af_packet.c
> @@ -1927,7 +1927,7 @@ retry:
> goto out_unlock;
> }
>
> - sockc.tsflags = 0;
> + sockc.tsflags = sk->sk_tsflags;
> if (msg->msg_controllen) {
> err = sock_cmsg_send(sk, msg, &sockc);
> if (unlikely(err)) {
> @@ -2678,7 +2678,7 @@ static int tpacket_snd(struct packet_sock *po, struct msghdr *msg)
> dev = dev_get_by_index(sock_net(&po->sk), saddr->sll_ifindex);
> }
>
> - sockc.tsflags = 0;
> + sockc.tsflags = po->sk.sk_tsflags;
> if (msg->msg_controllen) {
> err = sock_cmsg_send(&po->sk, msg, &sockc);
> if (unlikely(err))
> @@ -2881,7 +2881,7 @@ static int packet_snd(struct socket *sock, struct msghdr *msg, size_t len)
> if (unlikely(!(dev->flags & IFF_UP)))
> goto out_unlock;
>
> - sockc.tsflags = 0;
> + sockc.tsflags = sk->sk_tsflags;
> sockc.mark = sk->sk_mark;
> if (msg->msg_controllen) {
> err = sock_cmsg_send(sk, msg, &sockc);
> --
> 1.9.1
>
Thanks for the fix.
next prev parent reply other threads:[~2016-07-19 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 5:40 [PATCH v3] packet: fix second argument of sock_tx_timestamp() Yoshihiro Shimoda
2016-07-19 12:34 ` Soheil Hassas Yeganeh [this message]
2016-07-19 16:31 ` Willem de Bruijn
2016-07-20 4:01 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACSApvYj5X166euM2Qy+ubvLYdfYg65itMYiVeTf5SUuiA+gog@mail.gmail.com \
--to=soheil@google.com \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=fruggeri@aristanetworks.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tklauser@distanz.ch \
--cc=willemb@google.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).