[LIBS PLUGINS] Accessors to libs state tables fields - 2

[incertum]

See the previous issue #1712.
This issue is to track obtaining access to additional critical libs state data.

The approach will be similar to the recent extensions regarding how to access the proc args and fd tables.

---

• user & group info

falcosecurity::table_field m_uid
falcosecurity::table_field m_user
falcosecurity::table_field m_loginuid
falcosecurity::table_field m_loginuser

• capabilities

falcosecurity::table_field m_cap_permitted
falcosecurity::table_field m_cap_inheritable
falcosecurity::table_field m_cap_effective

• container data
• uint32_t sinsp_threadinfo::m_flags flags
• libs lastevent_fd_field per thread cache instance mtinfo

falcosecurity::table_field m_lastevent_fd_field

// Maybe while here just open up all of them
int64_t m_lastevent_fd; ///< The FD os the last event used by this thread.
uint64_t m_lastevent_ts; ///< timestamp of the last event for this thread.
uint64_t m_prevevent_ts; ///< timestamp of the event before the last for this thread.
uint64_t m_lastaccess_ts; ///< The last time this thread was looked up. Used when cleaning up the table.
uint64_t m_clone_ts; ///< When the clone that started this process happened.
uint64_t m_lastexec_ts; ///< The last time exec was called

---

fdinfo - Make all members accesible

• scap_fd_type m_type

falcosecurity::table_field m_fd_type_value;

• sinsp_sockinfo m_sockinfo

falcosecurity::table_field m_fd_sockinfo_value;

This will be a challenging task due to the numerous custom sub-data structures we have. However, without access to these structures, we are unable to support most of the network-related fd.* filtercheck fields through custom logic within a syscalls plugin.

union sinsp_sockinfo
{
	ipv4tuple m_ipv4info; ///< The tuple if this an IPv4 socket.
	ipv6tuple m_ipv6info; ///< The tuple if this an IPv6 socket.
	ipv4serverinfo m_ipv4serverinfo;  ///< Information about an IPv4 server socket.
	ipv6serverinfo m_ipv6serverinfo; ///< Information about an IPv6 server socket.
	unix_tuple m_unixinfo; ///< The tuple if this a unix socket.
};
...

---

Additional random comments:

• Uncertain how we would or could access the corresponding enter event, if applicable.
• How do we get the main thread?

---

TBD what other data structures shall be made accessible.

[incertum]

@jasondellaluce as requested attempted to update the initial comment to reflect a more detailed view of pending tasks #1944 (comment). Thanks.

[incertum]

/milestone TBD

/assign @jasondellaluce