linux-kernel - oom on wireless network saturation

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: <20f65d530709250103s556231a5vbb3741e11197df6c@mail.gmail.com>
Date:	Tue, 25 Sep 2007 20:03:27 +1200
From:	"Keith Chew" <keith.chew@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: oom on wireless network saturation

Hi

We are stress testing the wireless network driver on our linux system.
We use ping flood to saturate the network, and within 24 hours, we
managed to crash the driver.

This was a good test, as it hightlighted a timer problem in the
driver. After fixing that, we are now getting out of memory errors.
The OOM killer starts to kick in and the system freezes.

Can someone advise at a high level, what should the network driver do
in such a scenario? Essentially, the wireless packets get queued up in
the driver and eventually it just breaks. What is the correct way to
handle this gracefully?

Regards
Keith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/