[lustre-devel] prevent lustre from using specific ports for socket connections

[Defazio, Gian-Carlo]

Hi,

Is it possible to prevent lustre from using specific ports when establishing a socket connection?
We have the situation where lustre may use a port (1022) and then a service that needs to use that port fails to start.

Our current solution is a local patch to check the port values being iterated through in lnet/lnet/acceptor.c:lnet_connect() and to just skip over 1022.

Is there already a way to avoid certain ports for lustre? Either in lustre or via some kernel mechanism that would affect lustre?

We're considering making a more general patch that would allow specifying ports to avoid by adding a module parameter to lnet but aren't sure what a good design would be. So far, the basic idea is that the user supplies a string of numbers/ranges such as "512,513-515,1022" and then a list or bitmap or some other data structure of ports to avoid is created and then lnet_connect() checks that data structure when selecting ports.

Thanks,
Gian-Carlo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20250306/4af917b8/attachment.htm>