On Fri, Feb 15, 2019 at 7:42 AM Yafang Shao <laoar.s...@gmail.com> wrote: > > On Fri, Feb 15, 2019 at 10:58 PM Eric Dumazet <eduma...@google.com> wrote: > > > > On Fri, Feb 15, 2019 at 6:50 AM Yafang Shao <laoar.s...@gmail.com> wrote: > > > > > > As SOCK_DEBUG() isn't used any more, we can get ride of it now. > > > > > > > No, we are still using this infrastructure from time to time. > > > > I told you I agreed to remove the current (obsolete) TCP call sites, > > I never suggested to remove SOCK_DEBUG() completely. > > All right, however I'm not persuaded by you. > Because SOCK_DEBUG() is not a smart way for debugging, which requires > the user code to be modified. > We have other more flexible methords.
That might be the case, but only if you get enough privileges and skills. I fail to see why we should enforce anything here. It costs nothing having this interface kept. In any case, we do not deprecate features without a Documentation/ABI/obsolete/* file and quarantine.
