linux-kernel - Re: New thread: page allocation failure with E1000 (seems to be reproducible)

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

Message-ID: <2d460de71003010934m76594f4fk2e0b505b1867538c@mail.gmail.com>
Date:	Mon, 1 Mar 2010 18:34:25 +0100
From:	Richard Hartmann <richih.mailinglist@...il.com>
To:	Jesse Brandeburg <jesse.brandeburg@...il.com>
Cc:	e1000-devel@...ts.sf.net, linux-kernel@...r.kernel.org,
	Andrew Pochinsky <avp@....edu>
Subject: Re: New thread: page allocation failure with E1000 (seems to be 
	reproducible)

Hi Jesse,

> the memory allocation (order:0), while unexpected, are not fatal, and
> the e1000 driver is written to handle the failures during allocation.
>
> Does something else happen to the system after this or does operation continue?

I can not be sure, but I _think_ some bogus data made it into userspace.
I did have some binary in a text string I received & logged, which is a
tad unusual.


> You might be able to try the sysctl tweak to reserve a little more
> memory for driver allocations.
> # sysctl vm.min_free_kbytes
> # sysctl -e vm.min_free_kbytes=<double what you have>

I will try that, thanks.


> have you increased the number of rx/tx descriptors in use by e1000?

No. Should I?



Thanks,
Richard
--
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/