linux-kernel - Re: Problem with 2.6.18: memory leak(?)

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: <20061128064236.GA19797@night.netis.ru>
Date:	Tue, 28 Nov 2006 09:42:36 +0300
From:	"Alexander V. Lukyanov" <lav@...is.ru>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Problem with 2.6.18: memory leak(?)

On Mon, Nov 27, 2006 at 07:38:34PM -0800, Andrew Morton wrote:
> It's not necessarily a leak.  Networking tried to allocate two

You are right, it is not a leak. Probably the memory usage increased for some
other reason.

> physically-contiguous pages from atomic context, but no such two pages were
> available.  The packet will be dropped and things should recover.
> 
> Increasing /proc/sys/vm/min_free_kbytes will reduce the frequency somewhat.
> If it's actually a problem, which I doubt?

It is a problem. The messages load syslog and thus disk, network performance
decreases due to lost packets. I'll try to increase min_free_kbytes and
see if it helps.

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