From: Yafang Shao <laoar.shao@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, edumazet@google.com,
netdev@vger.kernel.org, shaoyafang@didiglobal.com,
Yafang Shao <laoar.shao@gmail.com>
Subject: [net-next 0/5] clean up SOCK_DEBUG()
Date: Fri, 15 Feb 2019 22:49:42 +0800 [thread overview]
Message-ID: <1550242187-29660-1-git-send-email-laoar.shao@gmail.com> (raw)
Per discussion with Daniel[1] and Eric[2], the SOCK_DEBUG() is a very
ancient interface, which is not very useful for debugging.
So we'd better clean up it.
After this patchset, the SO_DEBUG interface will not take any effect,
but I still keep it as-is in sock_{s,g}etsockopt() to avoid breaking
applications.
[1] https://patchwork.ozlabs.org/patch/1035573/
[2] https://patchwork.ozlabs.org/patch/1040533
Yafang Shao (5):
tcp: clean up SOCK_DEBUG()
x25: clean up SOCK_DEBUG()
appletalk: clean up SOCK_DEBUG()
dccp: clean up SOCK_DEBUG()
net: sock: remove the definition of SOCK_DEBUG()
include/net/sock.h | 19 -------------------
net/appletalk/ddp.c | 14 --------------
net/core/sock.c | 3 +++
net/dccp/ipv6.c | 2 --
net/ipv4/tcp_input.c | 19 +------------------
net/ipv6/tcp_ipv6.c | 2 --
net/x25/af_x25.c | 12 ------------
net/x25/x25_facilities.c | 32 ++++++++++----------------------
net/x25/x25_out.c | 4 +---
9 files changed, 15 insertions(+), 92 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-02-15 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 14:49 Yafang Shao [this message]
2019-02-15 14:49 ` [net-next 1/5] tcp: clean up SOCK_DEBUG() Yafang Shao
2019-02-15 14:49 ` [net-next 2/5] x25: " Yafang Shao
2019-02-15 14:49 ` [net-next 3/5] appletalk: " Yafang Shao
2019-02-15 14:49 ` [net-next 4/5] dccp: " Yafang Shao
2019-02-15 14:49 ` [net-next 5/5] net: sock: remove the definition of SOCK_DEBUG() Yafang Shao
2019-02-15 14:58 ` Eric Dumazet
2019-02-15 15:41 ` Yafang Shao
2019-02-15 15:54 ` Eric Dumazet
2019-02-15 18:12 ` Cong Wang
2019-02-15 18:22 ` Eric Dumazet
2019-02-15 18:51 ` Joe Perches
2019-02-16 2:50 ` 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=1550242187-29660-1-git-send-email-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=shaoyafang@didiglobal.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).