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  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:   Tue, 25 Aug 2020 10:52:57 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 209037] New: lec_seq_next does not update index position



Begin forwarded message:

Date: Tue, 25 Aug 2020 16:10:37 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 209037] New: lec_seq_next does not update index position


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

            Bug ID: 209037
           Summary: lec_seq_next does not update index position
           Product: Networking
           Version: 2.5
    Kernel Version: from at least 2.6.12+
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Other
          Assignee: stephen@...workplumber.org
          Reporter: colin.king@...onical.com
        Regression: No

Stress-testing /procfs with stress-ng tripped the following warning when
reading /proc/net/atm/lec:

[ 7236.344619] seq_file: buggy .next function lec_seq_next [lec] did not update
position index
[ 7236.344704] seq_file: buggy .next function lec_seq_next [lec] did not update
position index

can be reproduced by seeking on the proc file and reading:

dd if=/proc/net/atm/lec seek=1 of=/dev/stdout bs=1K

the read() also blocks which is not correct either.

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

Powered by blists - more mailing lists