From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH iproute2] ss: Tell user about -EOPNOTSUPP for SOCK_DESTROY Date: Wed, 18 May 2016 11:51:08 -0700 Message-ID: <20160518115108.46fabd49@xeon-e3> References: <1463442791-2399-1-git-send-email-dsa@cumulusnetworks.com> <1463442791-2399-2-git-send-email-dsa@cumulusnetworks.com> <39db6a27-9dfa-1c9a-2699-2f01a0e64a66@cumulusnetworks.com> <3d0fd83a-fa88-8ceb-a44d-237f5a005eb4@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Lorenzo Colitti , David Ahern , netdev@vger.kernel.org, netdev-owner@vger.kernel.org To: subashab@codeaurora.org Return-path: Received: from mail-pa0-f50.google.com ([209.85.220.50]:32850 "EHLO mail-pa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753477AbcERSu7 (ORCPT ); Wed, 18 May 2016 14:50:59 -0400 Received: by mail-pa0-f50.google.com with SMTP id xk12so20479054pac.0 for ; Wed, 18 May 2016 11:50:59 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 17 May 2016 12:35:53 -0600 subashab@codeaurora.org wrote: > On 2016-05-16 20:29, Lorenzo Colitti wrote: > > On Tue, May 17, 2016 at 11:24 AM, David Ahern > > wrote: > >> As I mentioned we can print the unsupported once or per socket matched > >> and > >> with the socket params. e.g., > >> > >> + } else if (errno == EOPNOTSUPP) { > >> + printf("Operation not supported for:\n"); > >> + inet_show_sock(h, diag_arg->f, > >> diag_arg->protocol); > >> > >> Actively suppressing all error messages is just wrong. I get the > >> flooding > >> issue so I'm fine with just printing it once. > > > > I disagree, but then I'm the one who wrote it in the first place, so > > you wouldn't expect me to agree. :-) Let's see what Stephen says. > > Hi Lorenzo > > Would it be acceptable to have a separate column which displays the > result of the sock destroy operation per socket. > State ... Killed > ESTAB Y > TIME_WAIT N > > If it is not supported from kernel, maybe print U (unsupported) for > this. When you guys come to a conclusion, then I will review the result. Right now neither solution looks good.