On Thu, Jul 10, 2025 at 05:57:23PM +0100, Lorenzo Stoakes wrote:
On Thu, Jul 10, 2025 at 07:22:49PM +0800, wang lian wrote:
+#include <linux/pidfd.h>
However, the pidfd tests already have a stub in so you can alternatively use:
#include "../pidfd/pidfd.h"
As is done in guard-regions.c.
One thing to watch out for with peering into the private header files of other selftests is that it's a routine source of build and sometimes runtime failures, people have a tendency to update one selftest without thinking that other selftests might be peering at their code. The cross tree aspect can make it painful to deal with the resulting issues.