netdev - Re: RFH, where did I go wrong?

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <cd3867e0-b645-c6cd-3464-29ffb142de5e@tarent.de>
Date:   Sun, 11 Sep 2022 01:43:38 +0200 (CEST)
From:   Thorsten Glaser <t.glaser@...ent.de>
To:     Haye.Haehne@...ekom.de, Sergey Ryazanov <ryazanov.s.a@...il.com>
cc:     netdev@...r.kernel.org
Subject: Re: RFH, where did I go wrong?

Hi Sergey,

> BTW, the stack backtrace contains only RTNL related functions. Does
> this warning appear when trying to reconfigure the qdisc? If so, then
> the error is probably somewhere in the qdisc configuration code. Such

good point. The qdisc is used in a mode where it’s reconfigured multiple
times per second, although I do not know if my colleague used it like
this or if the issue also happens when statically configuring.

@Haye: does it also crash for you if you don’t run the playlist but just
configure the qdisc with just the tc qdisc add … rate 20m command?

I did not have access to my test VM until today, so I’ll be able to look
into this more next week.

Thanks,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
╱ ╲ header encryption!
                        ****************************************************