[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR12MB326678FFB34C9141AD73853BD3DD0@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Mon, 13 Apr 2020 09:01:32 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
CC: Leon Romanovsky <leonro@...lanox.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Cong Wang <xiyou.wangcong@...il.com>,
"Jamal Hadi Salim" <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net v1] net/sched: Don't print dump stack in event of
transmission timeout
From: Leon Romanovsky <leon@...nel.org>
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.
And actually, can you please explain why BQL is not suppressing your
timeouts ?
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists