Project

General

Profile

Bug #5652

Memory leaks in klmmod after suspend/resume

Added by Marcel Telka over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
nfs - NFS server and client
Start date:
2015-02-24
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

When there is an active NFSv3 lock and you do the suspend/resume cycle, you'll end up with several memory leaks:

authkern_cache leak: 3 buffers, 72 bytes each, 216 bytes total
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS
ffffff00e7c11468 ffffff00e7a01e48      3b98272cdc5 ffffff00fa004840
                 ffffff00e2ccca08 ffffff00c5a62200 ffffff00c6802760
                 kmem_cache_alloc_debug+0x2e0
                 kmem_cache_alloc+0xdd
                 authkern_create+0x12
                 clnt_cots_kcreate+0x9d
                 clnt_tli_kcreate+0x2d5
                 nlm_nsm_init+0x152
                 nlm_resume_zone+0xb9
                 nlm_cprresume+0x38
                 lm_cprresume+9
                 0xfffffffff7fe1b98   
                 0xfffffffff7fe27c7   
                 0xfffffffff7fe18f8   
                 0xfffffffff7fe34b1   
                 stubs_common_code+0x51
                 kadmin+0x198         

authkern_cache leak: 3 buffers, 72 bytes each, 216 bytes total
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS                                      
ffffff00e7c11540 ffffff00e7a01de8      3b98272d5d6 ffffff00fa004840
                 ffffff00e2ccca08 ffffff00c5a62440                0
                 kmem_cache_alloc_debug+0x2e0
                 kmem_cache_alloc+0x320
                 authkern_create+0x12 
                 clnt_cots_kcreate+0x9d
                 clnt_tli_kcreate+0x2d5
                 nlm_nsm_init+0x18f   
                 nlm_resume_zone+0xb9 
                 nlm_cprresume+0x38   
                 lm_cprresume+9
                 0xfffffffff7fe1b98   
                 0xfffffffff7fe27c7   
                 0xfffffffff7fe18f8   
                 0xfffffffff7fe34b1   
                 stubs_common_code+0x51
                 kadmin+0x198         

authkern_cache leak: 1 buffer, 72 bytes
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS                                      
ffffff00e7c112b8 ffffff00e7a01f08       2f31c0342a ffffff00e77d74c0
                 ffffff00e2ccca08 ffffff00c49a44c0                0
                 kmem_cache_alloc_debug+0x2e0
                 kmem_cache_alloc+0x320
                 authkern_create+0x12 
                 clnt_cots_kcreate+0x9d
                 clnt_tli_kcreate+0x2d5
                 nlm_nsm_init+0x18f   
                 nlm_nsm_init_local+0x73
                 nlm_svc_starting+0x81
                 lm_svc+0x1ae         
                 nfssys+0x7b9         

authkern_cache leak: 1 buffer, 72 bytes
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS                                      
ffffff00e7c111e0 ffffff00e7a01f68       2f31c02ef6 ffffff00e77d74c0
                 ffffff00e2ccca08 ffffff00c49a4280 ffffff00c5eac728
                 kmem_cache_alloc_debug+0x2e0
                 kmem_cache_alloc+0xdd
                 authkern_create+0x12 
                 clnt_cots_kcreate+0x9d
                 clnt_tli_kcreate+0x2d5
                 nlm_nsm_init+0x152
                 nlm_nsm_init_local+0x73
                 nlm_svc_starting+0x81
                 lm_svc+0x1ae         
                 nfssys+0x7b9

History

#1

Updated by Marcel Telka over 5 years ago

The super easy way to reproduce the leak:

# svcadm restart nlockmgr

Also available in: Atom PDF