[LU-6480] leak cmid in kiblnd_dev_need_failover Created: 21/Apr/15  Updated: 26/Aug/15  Resolved: 26/Aug/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.8.0

Type: Bug Priority: Minor
Reporter: Liang Zhen (Inactive) Assignee: Liang Zhen (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-6495 push Fujitsu IB multi-rail patch to G... Closed
is related to LU-6531 Fujitsu's o2iblnd Channel Bonding Sol... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

cmid created by kiblnd_dev_need_failover should always be destroyed, however it is not the case in current implementation so we will leak a cmid on each time call of this function. Fortunately this leak can only happen when dev_failover is enabled.



 Comments   
Comment by Isaac Huang (Inactive) [ 21/Apr/15 ]

It seemed to happen only if actual device failover has happened under the IB bonding device. Very rare I'd say.

Comment by Gerrit Updater [ 27/Apr/15 ]

Liang Zhen (liang.zhen@intel.com) uploaded a new patch: http://review.whamcloud.com/14603
Subject: LU-6480 o2iblnd: leak cmid in kiblnd_dev_need_failover
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 795c7a3a009e524dfe103dd0d129648963169fcb

Comment by Gerrit Updater [ 26/Aug/15 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/14603/
Subject: LU-6480 o2iblnd: leak cmid in kiblnd_dev_need_failover
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 6646307454ff710bcff5df71de398e60b00f494e

Comment by Joseph Gmitter (Inactive) [ 26/Aug/15 ]

Landed for 2.8.

Generated at Sat Feb 10 02:00:35 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.