struct sss_cli_mc_ctx added fd_inode, ensure that open and close fd are

[answer9030]

Save the inode number while opening the file, and verify the inode number when closing the file to ensure that the same file is being opened and closed.

Used to solve the following issue:

[alexey-tikhonov]

This approach won't solve your issue (#6986) because "for(int fd = 3; fd <= 32; ++fd) { close(fd);" will close a socket used for communication with sssd_nss as well. And next sss_client will try to write to fd opened by your code (tcp socket or whatever).

[answer9030]

This approach won't solve your issue (#6986) because "for(int fd = 3; fd <= 32; ++fd) { close(fd);" will close a socket used for communication with sssd_nss as well. And next sss_client will try to write to fd opened by your code (tcp socket or whatever).

The socket will indeed be closed, and the corresponding fd may already be another file, but the purpose of my modification is to avoid libnss_ sss.so closes files opened by the process to avoid causing larger problems

[answer9030]

And I have a question, why not close "/var/lib/sss/mc/*" 'fd after mmap?

[alexey-tikhonov]

And I have a question, why not close "/var/lib/sss/mc/*" 'fd after mmap?

It's used in sss_nss_mc_validate()

[pbrezina]

Thank you for your contribution, we are certainly happy that people are willing to look into the code and submit a patch. However, I agree with Alexey, that this is not a solution for your case which needs to be fixed in your code. See: #6986 (comment) for details.

[answer9030]

I think that libnss_ sss.so should adapt to various applications, rather than allowing applications to adapt to libnss_ sss.so. And SSSD's fds are invisible to applications, making it difficult for applications to adapt to libnss_ Sss.so.

[answer9030]

Before closing Unix socket, the inode was verified. And I think the inode should also be verified here

[alexey-tikhonov]

@answer9030 , is software in question - tigervnc?