Feat(Linux): Add new process flags

[PaulDance]

Description

This adds two new/missing PF_* task flags to the Linux-like platform module:

• PF_BLOCK_TS that was added relatively recently, in 6.9;
• PF_SUSPEND_TASK that has been there for a bit more time: 3.11;

This would be for fanotify consumption. It should be easily backportable to 0.2.

Sources

https://github.com/torvalds/linux/blob/2ba9f676d0a2e408aef14d679984c26373bf37b7/include/linux/sched.h#L1661

Checklist

• Relevant tests in libc-test/semver have been updated
• No placeholder or unstable values like *LAST or *MAX are
  included (see #3131)
• Tested locally (cd libc-test && cargo test --target mytarget);
  especially relevant for platforms that may not be checked in CI

[rustbot]

r? @tgross35

rustbot has assigned @tgross35.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[PaulDance]

The error in https://github.com/rust-lang/libc/actions/runs/12201653969/job/34040533674?pr=4174 seems unrelated to my changes, no?

[tgross35]

The changes look good to me but could you update libc-test/semver/linux.txt? If you wouldn't mind squashing the first and third commit ("Add new process flags" and " Add PF_BLOCK_TS to libc-test/build.rs") that would also be nice to keep tests passing after each (no worries if not, I can do it before merge).

The error in https://github.com/rust-lang/libc/actions/runs/12201653969/job/34040533674?pr=4174 seems unrelated to my changes, no?

Indeed, looks like a new lint was added. If you're up to it feel free to add a patch with:

#[allow(unpredictable_function_pointer_comparisons)] // FIXME(msrv): stabilized in 1.85

Otherwise I'll get it at some point before merging this.

@rustbot label +stable-nominated

[tgross35]

Fyi I have a fix for the lint in progress #4177

[PaulDance]

The changes look good to me

👍

could you update libc-test/semver/linux.txt?

I wanted to as well, but couldn't see any of the previous PF_* constants in there, so I thought it was on purpose for some reason. Should I still put them all there or only the ones I added?

If you wouldn't mind squashing the first and third commit

Can do!

I have a fix for the lint in progress #4177

I see that, thanks! I'll rebase on top of it once merged.

[tgross35]

I wanted to as well, but couldn't see any of the previous PF_* constants in there, so I thought it was on purpose for some reason. Should I still put them all there or only the ones I added?

I can't think of any reason so I would just put them all there, I guess if it causes CI to fail for some reason then I'll change my answer :) thanks for offering.

[tgross35]

LGTM, thanks for the changes!

[PaulDance]

Cool, thanks!