netdev - Fw: [Bug 215329] New: The vsock component triggers out of memory when sending small packets.

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

Message-ID: <20211215073807.30c0041d@hermes.local>
Date:   Wed, 15 Dec 2021 07:38:36 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     sgarzare@...hat.com
Cc:     netdev@...r.kernel.org
Subject: Fw: [Bug 215329] New: The vsock component triggers out of memory
 when sending small packets.

Begin forwarded message:

Date: Wed, 15 Dec 2021 03:40:59 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 215329] New: The vsock component triggers out of memory when sending small packets.

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

            Bug ID: 215329
           Summary: The vsock component triggers out of memory when
                    sending small packets.
           Product: Networking
           Version: 2.5
    Kernel Version: 4.19.90
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@...workplumber.org
          Reporter: kircherlike@...look.com
        Regression: No

The memory usage of the vsock component when sending small packets is much
higher than that when sending large packets. When the VM memory is
insufficient, the out of memory is triggered.

Server（host）：iperf3 --vsock -s 2
Client（guest）：iperf3 --vsock -c 2 -t 10000 -l 1 -P 100

Slab information of kernel kmalloc in the 1 KB data packet is sent. The values
of kmalloc-256 and kmalloc-4096 are significantly higher than those in the
normal environment.

Traffic sending environment:
kmalloc-8192 68 68 8192 4 8 : tunables 0 0 0 : slabdata 17 17 0
kmalloc-4096 1186 1224 4096 8 8 : tunables 0 0 0 : slabdata 153 153 0
kmalloc-2048 965 992 2048 16 8 : tunables 0 0 0 : slabdata 62 62 0
kmalloc-1024 967 1040 1024 16 4 : tunables 0 0 0 : slabdata 65 65 0
kmalloc-512 1120 1120 512 16 2 : tunables 0 0 0 : slabdata 70 70 0
kmalloc-256 19644992 19644992 256 16 1 : tunables 0 0 0 : slabdata 1227812
1227812 0
kmalloc-128 760027 762656 128 32 1 : tunables 0 0 0 : slabdata 23833 23833 0

Normal environment:
kmalloc-8192 68 68 8192 4 8 : tunables 0 0 0 : slabdata 17 17 0
kmalloc-4096 1248 1248 4096 8 8 : tunables 0 0 0 : slabdata 156 156 0
kmalloc-2048 1008 1040 2048 16 8 : tunables 0 0 0 : slabdata 65 65 0
kmalloc-1024 948 960 1024 16 4 : tunables 0 0 0 : slabdata 60 60 0
kmalloc-512 1072 1072 512 16 2 : tunables 0 0 0 : slabdata 67 67 0
kmalloc-256 3199 3264 256 16 1 : tunables 0 0 0 : slabdata 204 204 0
kmalloc-128 761575 762080 128 32 1 : tunables 0 0 0 : slabdata 23815 23815 0

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

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