You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This is a page tracks issues that we run into while testing the Multi-Rail Feature

Problem List

  • with 17 interfaces trying to discover on the 17th interface returns an error "no route to host". This is an intermittent issue. Attempting to reproduce
  • With 17 interface discovered "show peer" hangs
    • When the rc from the kernel is not 0. The structure is not copied out of the kernel to user space. The code depends on that in order to pass the new size if the data to be copied out is too big for the buffer passed in by the user. Since that doesn't happen when rc == -E2BIG, user space code gets into an infinite loop sending IOCTLs to the kernel
    • from libcfs_ioctl()
 
145 »·······»·······»·······if (err == 0) {
146 »·······»·······»·······»·······if (copy_to_user(uparam, hdr, hdr->ioc_len))
147 »·······»·······»·······»·······»·······err = -EFAULT;
148 »·······»·······»·······}
149 »·······»·······»·······break;


The buffer is only copied to user space if the ioctl handler returns 0. Not really sure if it's safe to change that.
  • "lnetctl discover" command hangs with discovery off. This happened once, so an intermittent issue. Will try to reproduce.
  • "lnetctl discover" discovers the peer even with discovery off.

  • Doug: I configured a Parallels VM with 16 interfaces (won't let me do 17 as 16 is a limit).  When I "lctl network configure" with no YAML or module parameters, I get this error from ksocklnd: "Mar 7 14:01:16 centos-7 kernel: LNet: 5111:0:(socklnd.c:2652:ksocknal_enumerate_interfaces()) Ignoring interface virbr0 (too many interfaces)".

  • No labels