From mboxrd@z Thu Jan 1 00:00:00 1970 From: subashab@codeaurora.org Subject: Re: [PATCH iproute2] ss: Tell user about -EOPNOTSUPP for SOCK_DESTROY Date: Tue, 17 May 2016 12:35:53 -0600 Message-ID: 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; format=flowed Content-Transfer-Encoding: 7bit Cc: David Ahern , Stephen Hemminger , netdev@vger.kernel.org, netdev-owner@vger.kernel.org To: Lorenzo Colitti Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:38427 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752084AbcEQSf4 (ORCPT ); Tue, 17 May 2016 14:35:56 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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.