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]
Message-ID: <20220426075448.037015eb@hermes.local>
Date:   Tue, 26 Apr 2022 07:54:48 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 215888] New: raw socket test with stress-ng trigger soft
 lockup



Begin forwarded message:

Date: Tue, 26 Apr 2022 09:31:50 +0000
From: bugzilla-daemon@...nel.org
To: stephen@...workplumber.org
Subject: [Bug 215888] New: raw socket test with stress-ng trigger soft lockup


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

            Bug ID: 215888
           Summary: raw socket test with stress-ng trigger soft lockup
           Product: Networking
           Version: 2.5
    Kernel Version: 5.17
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
          Assignee: stephen@...workplumber.org
          Reporter: colin.king@...onical.com
        Regression: No

Running stress-ng [1] with the following raw socket stressor triggers a
softlockup on a SMP NUMA x86-64 system:

sudo stress-ng --rawsock 20 -t 60

kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [stress-ng:49781]

Tested this on 5.17. User has also reported this against the stress-ng project:

https://github.com/ColinIanKing/stress-ng/issues/187

[1] Stress-ng:
https://github.com/ColinIanKing/stress-ng
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make
sudo ./stress-ng --rawsock 0 -t 60

-- 
You may reply to this email to add a comment.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ