[LU-16573] kernel:LNetError: 214187:0:(nidstrings.c:704:libcfs_num_match()) ASSERTION( !list_empty(numaddr) ) failed: Created: 17/Feb/23  Updated: 22/Apr/23  Resolved: 22/Apr/23

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

Type: Bug Priority: Minor
Reporter: Chris Horn Assignee: Chris Horn
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   
[root@el8-mds1 crash]# cat /tmp/lnet.conf
net:
    - net type: tcp
      local NI(s):
        - interfaces:
              0: eth2
        - interfaces:
              0: eth3
udsp:
    - idx: 0
      src: tcp
      action:
          priority: 0
    - idx: 1
      dst: tcp
      action:
          priority: 0
[root@el8-mds1 crash]#

[root@el8-mds1 tests]# lnetctl import /tmp/lnet.conf
[root@el8-mds1 tests]# lnetctl udsp show
udsp:
    - idx: 0
      src: tcp
      dst: tcp
      rte: NA
      action:
          priority: 0
    - idx: 1
      src: NA
      dst: tcp
      rte: NA
      action:
          priority: 0
[root@el8-mds1 tests]# lnetctl ping --source 10.73.20.2@tcp 10.73.20.3@tcp
Connection to 127.0.0.1 closed.

loading this lnet configuration results in a mangled udsp configuration and causes the titular LBUG when any traffic occurs.



 Comments   
Comment by Gerrit Updater [ 07/Apr/23 ]

"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50576
Subject: LU-16573 lnet: Check empty list in cfs_match_nid_net
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: dea6c43f92c7294f3255ec70fff030dce0c24121

Comment by Gerrit Updater [ 22/Apr/23 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50576/
Subject: LU-16573 lnet: Check empty list in cfs_match_nid_net
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: f3ba286b05d557b0d8924923eaf8788aa595b1b7

Comment by Peter Jones [ 22/Apr/23 ]

Landed for 2.16

Generated at Sat Feb 10 03:28:11 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.