From: Yafang Shao <laoar.shao@gmail.com>
To: davem@davemloft.net, songliubraving@fb.com, marcelo.leitner@gmail.com
Cc: edumazet@google.com, xiyou.wangcong@gmail.com, mingo@redhat.com,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
rostedt@goodmis.org, bgregg@netflix.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH net-next 2/3] net:tracepoint: using sock_set_state tracepoint to trace DCCP state transition
Date: Sun, 10 Dec 2017 23:31:43 +0800 [thread overview]
Message-ID: <1512919904-14166-3-git-send-email-laoar.shao@gmail.com> (raw)
In-Reply-To: <1512919904-14166-1-git-send-email-laoar.shao@gmail.com>
With changes in inet_ files, DCCP state transitions are traced with
sock_set_state tracepoint.
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
---
net/dccp/proto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dccp/proto.c b/net/dccp/proto.c
index b68168f..92b9613 100644
--- a/net/dccp/proto.c
+++ b/net/dccp/proto.c
@@ -110,7 +110,7 @@ void dccp_set_state(struct sock *sk, const int state)
/* Change state AFTER socket is unhashed to avoid closed
* socket sitting in hash tables.
*/
- sk->sk_state = state;
+ sk_set_state(sk, state);
}
EXPORT_SYMBOL_GPL(dccp_set_state);
--
1.8.3.1
next prev parent reply other threads:[~2017-12-10 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 15:31 [PATCH net-next 0/3] replace tcp_set_state tracepoint with sock_set_state tracepoint Yafang Shao
2017-12-10 15:31 ` [PATCH net-next 1/3] net:tracepoint: " Yafang Shao
2017-12-13 1:19 ` Song Liu
2017-12-13 9:50 ` Yafang Shao
2017-12-10 15:31 ` Yafang Shao [this message]
2017-12-10 15:31 ` [PATCH net-next 3/3] net:tracepoint: using sock_set_state tracepoint to trace SCTP state transition Yafang Shao
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=1512919904-14166-3-git-send-email-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=bgregg@netflix.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/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
all inboxes | Powered by JetHome®