lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 13 Apr 2020 13:20:53 +0300
From:   Leon Romanovsky <>
To:     Jose Abreu <>
Cc:     "David S. Miller" <>,
        Jakub Kicinski <>,
        Arjan van de Ven <>,
        Cong Wang <>,
        Jamal Hadi Salim <>,
        Jiri Pirko <>,
        "" <>
Subject: Re: [PATCH net v1] net/sched: Don't print dump stack in event of
 transmission timeout

On Mon, Apr 13, 2020 at 09:01:32AM +0000, Jose Abreu wrote:
> From: Leon Romanovsky <>
> Date: Apr/12/2020, 07:08:54 (UTC+00:00)
> > [  281.170584] ------------[ cut here ]------------
> Not objecting to the patch it-self (because usually stack trace is
> useless), but just FYI we use this marker in our CI to track for timeouts
> or crashes. I'm not sure if anyone else is using it.

I didn't delete the "NETDEV WATCHDOG .." message and it will be still
visible as a marker.

> And actually, can you please explain why BQL is not suppressing your
> timeouts ?

Driver can't distinguish between "real" timeout and "mixed traffic" timeout,
so we don't want to completely disable "dev->netdev_ops->ndo_tx_timeout(dev, i);"
call in watchdog [1]. The goal is to leave functionality in place and
simply remove stack trace to be similar to other BUG prints in that file [2].


> ---
> Thanks,
> Jose Miguel Abreu

Powered by blists - more mailing lists