netdev - Fw: [Bug 208833] New: applying HFSC causes soft lockup (probably related to pppoe)

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>] [day] [month] [year] [list]

Date:   Thu, 6 Aug 2020 08:04:52 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 208833] New: applying HFSC causes soft lockup (probably
 related to pppoe)

Begin forwarded message:

Date: Thu, 06 Aug 2020 13:22:36 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 208833] New: applying HFSC causes soft lockup (probably related to pppoe)

https://bugzilla.kernel.org/show_bug.cgi?id=208833

            Bug ID: 208833
           Summary: applying HFSC causes soft lockup (probably related to
                    pppoe)
           Product: Networking
           Version: 2.5
    Kernel Version: 5.7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@...workplumber.org
          Reporter: valahanovich@....by
        Regression: No

Created attachment 290795
  --> https://bugzilla.kernel.org/attachment.cgi?id=290795&action=edit  
example of my regular tc script

Applying and reapplying HFSC qdisc to interface with heavy load often causes
soft lockup (in random processes, in short time after applying qdisc).

Stack trace was somewhat uninformative and hard to get. I mostly observe this
with torrent client on PPPOE client interface when run attached script several
times.

Will attach dmesg as soon as i will be able to reliably get it.
I tried to bisect bug, but stopped at some old kernel that won't even boot with
my config. So the problem could be old but unnoticed.

-- 
You are receiving this mail because:
You are the assignee for the bug.