From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f48.google.com ([209.85.160.48]:35930 "EHLO mail-pl0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754048AbeCRQLU (ORCPT ); Sun, 18 Mar 2018 12:11:20 -0400 Received: by mail-pl0-f48.google.com with SMTP id 61-v6so8791269plf.3 for ; Sun, 18 Mar 2018 09:11:20 -0700 (PDT) Subject: Re: [PATCH RFC 0/2] Add support for warnings to extack To: Marcelo Ricardo Leitner , netdev@vger.kernel.org Cc: Alexander Aring , Jiri Pirko , Jakub Kicinski References: From: David Ahern Message-ID: <5f894da5-6e45-c70c-e061-e7572a4390f1@gmail.com> Date: Sun, 18 Mar 2018 10:11:52 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On 3/16/18 1:23 PM, Marcelo Ricardo Leitner wrote: > Currently we have the limitation that warnings cannot be reported though > extack. For example, when tc flower failed to get offloaded but got > installed on software datapath. The hardware failure is not fatal and > thus extack is not even shared with the driver, so the error is simply > omitted from any logging. If this set ends up moving forward, the above statement needs to be corrected: extack allows non-error messages to be sent back to the user, so the above must be talking about some other limitation local to tc.