From: "Alexander V. Lukyanov" <lav@netis.ru>
To: linux-kernel@vger.kernel.org
Subject: Problem with 2.6.18: memory leak(?)
Date: Mon, 27 Nov 2006 15:44:44 +0300 [thread overview]
Message-ID: <20061127124443.GA11569@night.netis.ru> (raw)
After a while, a loaded http proxy gets many errors like below. It is
reproducible and happens again after reboot (in some time). It did not
happen with 2.6.17. I have also tested 2.6.18.3, the leak is there too.
swapper: page allocation failure. order:1, mode:0x20
[<c012bc40>] __alloc_pages+0x253/0x267
[<c013b12e>] cache_alloc_refill+0x243/0x3e7
[<c013b317>] __kmalloc+0x45/0x51
[<c01c11b8>] __alloc_skb+0x49/0xf4
[<c01e2feb>] tcp_collapse+0x10f/0x2ca
[<c01e32f5>] tcp_prune_queue+0x14f/0x20b
[<c01e3550>] tcp_data_queue+0x19f/0x9e9
[<c01ff7ea>] ipt_do_table+0x296/0x2c0
[<c01e52ef>] tcp_rcv_established+0x533/0x5c4
[<c01e9e2c>] tcp_v4_do_rcv+0x22/0x267
[<c01ff88a>] ipt_hook+0x17/0x1d
[<c01d04ad>] nf_iterate+0x30/0x61
[<c01ebe08>] tcp_v4_rcv+0x751/0x7a5
[<c01dd215>] tcp_prequeue_process+0x30/0x56
[<c01d59a8>] ip_local_deliver+0x12f/0x1ab
[<c01d5850>] ip_rcv+0x33f/0x368
[<c01c4991>] netif_receive_skb+0x135/0x176
[<c01c5da5>] process_backlog+0x6d/0xd2
[<c01c5e5c>] net_rx_action+0x52/0xcb
[<c0110463>] __do_softirq+0x35/0x75
[<c01104c5>] do_softirq+0x22/0x26
[<c0103b7f>] do_IRQ+0x45/0x4d
[<c010266a>] common_interrupt+0x1a/0x20
[<c0101506>] mwait_idle+0x20/0x33
[<c01014d1>] cpu_idle+0x39/0x4e
[<c02765f9>] start_kernel+0x275/0x277
Mem-info:
DMA per-cpu:
cpu 0 hot: high 0, batch 1 used:0
cpu 0 cold: high 0, batch 1 used:0
DMA32 per-cpu: empty
Normal per-cpu:
cpu 0 hot: high 186, batch 31 used:21
cpu 0 cold: high 62, batch 15 used:59
HighMem per-cpu: empty
Free pages: 27156kB (0kB HighMem)
Active:165330 inactive:5001 dirty:18 writeback:283 unstable:0 free:6789 slab:48830 mapped:415 pagetables:278
DMA free:3548kB min:68kB low:84kB high:100kB active:2404kB inactive:0kB present:16384kB pages_scanned:357 all_unreclaimable? no
lowmem_reserve[]: 0 0 880 880
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 880 880
Normal free:23608kB min:3756kB low:4692kB high:5632kB active:658916kB inactive:20004kB present:901120kB pages_scanned:772 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 281*4kB 71*8kB 26*16kB 3*32kB 1*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 3548kB
DMA32: empty
Normal: 5726*4kB 0*8kB 0*16kB 0*32kB 1*64kB 1*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 23608kB
HighMem: empty
Swap cache: add 2143636, delete 2050596, find 187393/808790, race 0+0
Free swap = 495296kB
Total swap = 1003972kB
Free swap: 495296kB
229376 pages of RAM
0 pages of HIGHMEM
2500 reserved pages
1450 pages shared
93040 pages swap cached
18 pages dirty
283 pages writeback
415 pages mapped
48830 pages slab
278 pages pagetables
next reply other threads:[~2006-11-27 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 12:44 Alexander V. Lukyanov [this message]
2006-11-28 3:38 ` Problem with 2.6.18: memory leak(?) Andrew Morton
2006-11-28 6:42 ` Alexander V. Lukyanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061127124443.GA11569@night.netis.ru \
--to=lav@netis.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox