From: Paul Rolland <rol@as2917.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: rol@as2917.net
Subject: 2.6.31-rc4 - slab entry tak_delay_info leaking ???
Date: Wed, 29 Jul 2009 08:20:47 +0200 [thread overview]
Message-ID: <20090729082047.048ee1a8@tux.DEF.witbe.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hello,
Since I'm running 2.6.31-rc? (3 or 4 I think), I often find my machine with
my X session killed in the morning, and the kdm login screen displayed.
This morning, I decided to save the /var/log/messages to check it before
rebooting, and saw that the OOM killer triggered during the night.
So, I quickly made a copy of it, and a slabtop output. There came the
surprise :
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
12899448 12899445 99% 0.11K 358318 36 1433272K
task_delay_info
On a freshly booted machine, the same entry shows :
3204 3191 99% 0.11K 89 36 356K task_delay_info
after the X session is started.
Please find attached the slabtop -o output.
Regards,
Paul
[-- Attachment #2: rol.crash2 --]
[-- Type: application/octet-stream, Size: 6087 bytes --]
Active / Total Objects (% used) : 13028835 / 13083680 (99.6%)
Active / Total Slabs (% used) : 364755 / 364755 (100.0%)
Active / Total Caches (% used) : 70 / 85 (82.4%)
Active / Total Size (% used) : 1444256.02K / 1453783.34K (99.3%)
Minimum / Average / Maximum Object : 0.01K / 0.11K / 8.00K
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
12899448 12899445 99% 0.11K 358318 36 1433272K task_delay_info
72936 31353 42% 0.11K 2026 36 8104K buffer_head
15246 11546 75% 0.55K 1089 14 8712K radix_tree_node
13176 12704 96% 0.16K 549 24 2196K vm_area_struct
12432 11510 92% 0.19K 592 21 2368K dentry
10965 10887 99% 0.08K 215 51 860K sysfs_dir_cache
10180 7976 78% 0.77K 509 20 8144K ext3_inode_cache
8295 8217 99% 0.19K 395 21 1580K kmalloc-192
5120 4080 79% 0.01K 10 512 40K kmalloc-8
4608 4198 91% 0.03K 36 128 144K kmalloc-32
4096 2619 63% 0.02K 16 256 64K kmalloc-16
4096 4047 98% 0.03K 32 128 128K anon_vma
3328 2370 71% 0.06K 52 64 208K kmalloc-64
2520 2228 88% 0.09K 60 42 240K kmalloc-96
2352 2351 99% 0.25K 147 16 588K kmalloc-256
2320 2320 100% 0.77K 116 20 1856K shmem_inode_cache
2256 2253 99% 1.00K 141 16 2256K kmalloc-1024
1176 1158 98% 0.07K 21 56 84K Acpi-ParseExt
1088 683 62% 0.12K 34 32 136K kmalloc-128
736 654 88% 0.50K 46 16 368K kmalloc-512
680 596 87% 0.02K 4 170 16K fsnotify_event_holder
615 511 83% 0.53K 41 15 328K idr_layer_cache
480 414 86% 0.62K 40 12 320K proc_inode_cache
391 357 91% 0.69K 17 23 272K files_cache
352 311 88% 2.00K 22 16 704K kmalloc-2048
345 318 92% 0.69K 15 23 240K sock_inode_cache
340 340 100% 0.02K 2 170 8K journal_handle
299 207 69% 0.58K 23 13 184K inode_cache
280 222 79% 1.58K 14 20 448K task_struct
270 145 53% 0.87K 15 18 240K ext4_inode_cache
256 256 100% 0.03K 2 128 8K revoke_record
256 256 100% 0.02K 1 256 4K revoke_table
208 208 100% 4.00K 26 8 832K kmalloc_dma-4096
187 161 86% 0.94K 11 17 176K signal_cache
180 150 83% 2.06K 12 15 384K sighand_cache
180 92 51% 0.11K 5 36 20K journal_head
170 170 100% 0.05K 2 85 8K Acpi-Parse
152 143 94% 4.00K 19 8 608K kmalloc-4096
146 73 50% 0.05K 2 73 8K uhci_urb_priv
146 146 100% 0.05K 2 73 8K ext4_free_block_extents
133 109 81% 0.81K 7 19 112K mm_struct
117 78 66% 0.10K 3 39 12K fsnotify_event
92 46 50% 0.09K 2 46 8K ext3_xattr
78 68 87% 0.15K 3 26 12K dm_crypt_io
75 52 69% 0.16K 3 25 12K sigqueue
60 40 66% 0.33K 5 12 20K blkdev_requests
56 56 100% 0.14K 2 28 8K ext4_alloc_context
54 53 98% 0.88K 3 18 48K bdev_cache
50 25 50% 0.62K 2 25 32K fuse_request
48 33 68% 1.93K 3 16 96K blkdev_queue
44 35 79% 8.00K 11 4 352K kmalloc-8192
44 44 100% 0.18K 2 22 8K file_lock_cache
42 42 100% 1.50K 2 21 64K TCP
42 42 100% 0.75K 2 21 32K UDP
42 42 100% 0.38K 2 21 16K ip_dst_cache
39 39 100% 0.10K 1 39 4K ext4_prealloc_space
36 36 100% 1.69K 2 18 64K TCPv6
34 34 100% 0.94K 2 17 32K UDPv6
32 32 100% 0.25K 2 16 8K tw_sock_TCP
32 32 100% 1.00K 2 16 32K kmalloc_dma-1024
32 32 100% 2.00K 2 16 64K kmalloc_dma-2048
30 30 100% 0.27K 2 15 8K nf_conntrack
24 24 100% 0.32K 2 12 8K taskstats
24 23 95% 0.31K 2 12 8K kioctx
24 24 100% 0.31K 2 12 8K tw_sock_TCPv6
21 21 100% 0.75K 1 21 16K RAW
21 21 100% 0.75K 1 21 16K fuse_inode
18 18 100% 0.88K 1 18 16K mqueue_inode_cache
16 16 100% 0.50K 1 16 8K kmalloc_dma-512
13 13 100% 0.58K 1 13 8K hugetlbfs_inode_cache
0 0 0% 0.75K 0 21 0K UDP-Lite
0 0 0% 2.06K 0 15 0K pid_namespace
next reply other threads:[~2009-07-29 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 6:20 Paul Rolland [this message]
2009-07-30 10:07 ` Paul Rolland
2009-07-30 10:26 ` Paul Rolland
2009-07-30 15:53 ` Catalin Marinas
2009-07-31 20:03 ` Paul Rolland
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=20090729082047.048ee1a8@tux.DEF.witbe.net \
--to=rol@as2917.net \
--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
Powered by JetHome