netdev - Re: [PATCH v3 net-next 0/5] replace tcp_set_state tracepoint with inet_sock_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20171220.140040.1247383563394752781.davem@davemloft.net>
Date:   Wed, 20 Dec 2017 14:00:40 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     laoar.shao@...il.com
Cc:     songliubraving@...com, marcelo.leitner@...il.com,
        rostedt@...dmis.org, bgregg@...flix.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 net-next 0/5] replace tcp_set_state tracepoint with
 inet_sock_set_state

From: Yafang Shao <laoar.shao@...il.com>
Date: Wed, 20 Dec 2017 11:12:49 +0800

> According to the discussion in the mail thread
> https://patchwork.kernel.org/patch/10099243/,
> tcp_set_state tracepoint is renamed to inet_sock_set_state tracepoint and is
> moved to include/trace/events/sock.h.
> 
> With this new tracepoint, we can trace AF_INET/AF_INET6 sock state transitions.
> As there's only one single tracepoint for inet, so I didn't create a new trace
> file named trace/events/inet_sock.h, and just place it in
> include/trace/events/sock.h
> 
> Currently TCP/DCCP/SCTP state transitions are traced with this tracepoint.
> 
> - Why not more protocol ?
> If we really think that anonter protocol should be traced, I will modify the
> code to trace it.
> I just want to make the code easy and not output useless information.

Series applied, thanks.