From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f178.google.com ([209.85.220.178]:46420 "EHLO mail-qk0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061AbeCRSUL (ORCPT ); Sun, 18 Mar 2018 14:20:11 -0400 Received: by mail-qk0-f178.google.com with SMTP id o184so16092673qkd.13 for ; Sun, 18 Mar 2018 11:20:10 -0700 (PDT) Date: Sun, 18 Mar 2018 15:20:01 -0300 From: Marcelo Ricardo Leitner To: David Ahern Cc: netdev@vger.kernel.org, Alexander Aring , Jiri Pirko , Jakub Kicinski Subject: Re: [PATCH RFC 0/2] Add support for warnings to extack Message-ID: <20180318182001.GH9345@localhost.localdomain> References: <5f894da5-6e45-c70c-e061-e7572a4390f1@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f894da5-6e45-c70c-e061-e7572a4390f1@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Sun, Mar 18, 2018 at 10:11:52AM -0600, David Ahern wrote: > 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. Right. Thanks, Marcelo