linux-kernel - Re: 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4

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

Message-ID: <alpine.DEB.2.00.0904221850360.17988@p34.internal.lan>
Date:	Wed, 22 Apr 2009 18:51:21 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Jesse Brandeburg <jesse.brandeburg@...il.com>
cc:	Aioanei Rares <krnl.list@...il.com>, linux-kernel@...r.kernel.org,
	linux-nfs@...r.kernel.org
Subject: Re: 2.6.29.1: Pid: 2831, comm: nfsd Not tainted 2.6.29.1 #4



On Wed, 22 Apr 2009, Jesse Brandeburg wrote:

> On Tue, Apr 21, 2009 at 1:00 PM, Aioanei Rares <krnl.list@...il.com> wrote:
>> Justin Piszcz wrote:
>>> This has been happening with 2.6.28.(x) and now 2.6.29.(x), can anyone
>>> suggest the possible root cause of this problem, re: the nfsd page
>>> allocation
>>> failures:
>
>> Yes, it happened to me too on a Debian unstable machine with more than one
>> kernel, starting with 2.6.28 until now. I have a feeling it's a
>> Debian-specific problem rather than a kernel one.
>
> you may both want to try
> echo 16384 > /proc/sys/vm/min_free_kbytes
>
> or some other value depending on your amount of ram.  This change will
> increase the minimum amount of memory available for network memory
> allocations, which are called from softirq context to refill the NIC's
> receive buffers.
>

Will give it a shot, the default was already pretty close to the 
suggestion, 11441, if it recurs, will increase further.

Thanks,

Justin.
--
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/