[LU-19918] `lnetctl import` segfaults on YAML route gateway containing NID range expression

• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Affects Version/s: Lustre 2.17.0
• Severity: 3
• Assignee: WC Triage
• Reporter: Kilian Cavalotti

Description

Description:

lnetctl import segfaults when the configuration file contains a route block with a NID range expression in the gateway field.

This appears to be a regression in 2.17, since importing NID ranges worked correctly in Lustre 2.15.

Steps to reproduce:

Create /etc/lnet.conf containing:

global:
    - retry_count: 2
    - transaction_timeout: 49
net:
    - net type: o2ib4
      local NI(s):
        - interfaces:
              0: ib0
route:
    - net: o2ib5
      gateway: 10.52.0.[131-134]@o2ib4

Importing that configuration file generates a segfault:

# lnetctl import /etc/lnet.conf
Segmentation fault

Quoting the gateway value (e.g. "10.52.0.[131-134]@o2ib4") does not help.

It still looks like a parsing issue somehow, since the equivalent lnetctl route add --net o2ib5 --gateway 10.52.0.[131-134]@o2ib4 command handles range expressions correctly and is not affected.