ci: upgrade checkout action and add front matter validation

Upgrade actions/checkout from v3 to v4. Add a validation step that
checks all feature Markdown files have proper YAML front matter,
catching malformed contributions before deploy.

Signed-off-by: Christian Brauner <brauner@kernel.org>

Author: brauner

.github/workflows/gh-pages.yml

@@ -13,7 +13,7 @@ jobs:
     concurrency:
       group: ${{ github.workflow }}-${{ github.ref }}
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           submodules: true
           fetch-depth: 0
@@ -27,6 +27,20 @@ jobs:
       - name: Build
         run: cd website && hugo --minify -d ../public
 
+      - name: Validate front matter
+        run: |
+          errors=0
+          for f in $(find website/content -name '*.md' ! -name '_index.md'); do
+            if ! head -1 "$f" | grep -q '^---$'; then
+              echo "ERROR: $f missing front matter"
+              errors=$((errors + 1))
+            fi
+          done
+          if [ "$errors" -gt 0 ]; then
+            echo "$errors file(s) with missing front matter"
+            exit 1
+          fi
+
       - name: Deploy
         uses: peaceiris/actions-gh-pages@v3
         if: ${{ github.ref == 'refs/heads/main' }}

README.md

@@ -35,7 +35,7 @@ cd kernel-features/website
 hugo server
 ```
 
-Requires [Hugo](https://gohugo.io/) (extended edition, v0.147.8+).
+Requires [Hugo](https://gohugo.io/) (extended edition).
 
 ## License
 

website/content/completed/api-to-determine-the-parent-process-id-of-a-pidfd.md

@@ -21,7 +21,7 @@ easily before even calling that syscall.
 
 **🙇 `cdda1f26e74b ("pidfd: add ioctl to retrieve pid info")` 🙇**
 
-**Usecase:** systemd manages a multitude of processes, most of which
+**Use-Case:** systemd manages a multitude of processes, most of which
 are its own children, but many which are not. It would be great if
 we could easily determine whether it is worth waiting for
 `SIGCHLD`/`waitid()` on them or whether waiting for `POLLIN` on

website/content/completed/make-statx-on-a-pidfd-return-additional-info.md

@@ -21,7 +21,7 @@ These fields should in particular be queriable *after* the process
 already exited and has been reaped, i.e. after its PID has already
 been recycled.
 
-**Usecase:** In systemd we maintain lists of processes in a hash
+**Use-Case:** In systemd we maintain lists of processes in a hash
 table. Right now, the key is the PID, but this is less than ideal
 because of PID recycling. By being able to use the `.stx_btime`
 and/or `.stx_ino` fields instead would be perfect to safely

website/content/completed/set-comm-field-before-exec.md

@@ -29,7 +29,7 @@ https://github.com/systemd/systemd/commit/8939eeae528ef9b9ad2a21995279b76d382d5c
 
 **🙇 `543841d18060 ("exec: fix up /proc/pid/comm in the execveat(AT_EMPTY_PATH) case")` 🙇**
 
-**Usecase:** In systemd we generally would prefer using `fexecve()`
+**Use-Case:** In systemd we generally would prefer using `fexecve()`
 to safely and race-freely invoke processes, but the fact that `comm`
 is useless after invoking a process that way makes the call
 unfortunately hard to use for systemd.

website/content/completed/take-ip-unicast-if-into-account-for-routing-decisions.md

@@ -3,7 +3,6 @@ title: "Take `IP_UNICAST_IF` into account for routing decisions"
 weight: 110
 status: completed
 categories:
-  - security
   - sockets
 commit: "0e4d354762cefd3e16b4cff8988ff276e45effc4"
 ---

website/content/in-progress/ability-to-put-user-xattrs-on-s-ifsock-socket-entrypoint-inodes-in-the-file.md

@@ -14,7 +14,7 @@ Currently, the kernel only allows extended attributes in the
 inodes. It would be tremendously useful to allow them to be
 associated with socket inodes, too.
 
-**Usecase:** There are two syslog RFCs in use today: RFC3164 and
+**Use-Case:** There are two syslog RFCs in use today: RFC3164 and
 RFC5424. `glibc`'s `syslog()` API generates events close to the
 former, but there are programs which would like to generate the
 latter instead (as it supports structured logging). The two formats

website/content/in-progress/create-empty-mount-namespaces-via-unshare-unshare-empty-mntns-and-clone3-clone.md

@@ -13,6 +13,6 @@ Now that we have support for `nullfs` it is trivial to allow the
 creation of completely empty mount namespaces, i.e., mount namespaces
 that only have the `nullfs` mount located at it's root.
 
-**Usecase:** This allows to isolate tasks in completely empty mount
+**Use-Case:** This allows to isolate tasks in completely empty mount
 namespaces. It also allows the caller to avoid copying its current mount
 table which is useless in the majority of container workload cases.

website/content/wishlist/add-process-by-pidfd-to-a-cgroup.md

@@ -17,7 +17,7 @@ hence can control that it hasn't been reaped yet, and hence
 guarantees the PID is valid. This is racy however if "foreign"
 processes shall be moved into the cgroup.
 
-**Usecase:** In systemd, all user sessions are wrapped in scope
+**Use-Case:** In systemd, all user sessions are wrapped in scope
 units which are backed by a cgroup. The session processes moved into
 the scope unit are typically "foreign" processes, i.e. not children
 of the service manager, hence doing the movement is subject to races

website/content/wishlist/at-empty-path-support-for-openat-and-openat2.md

@@ -3,7 +3,7 @@ title: "`AT_EMPTY_PATH` support for `openat()` and `openat2()`"
 weight: 420
 status: wishlist
 categories:
-  - general
+  - processes
 ---
 
 To get an operable version of an `O_PATH` file descriptors, it is
@@ -16,6 +16,3 @@ similar functions have `AT_EMPTY_PATH`.
 
 **Use-Case:** When dealing with `O_PATH` file descriptors, allow
 re-opening an operable version without the need of `procfs`.
-
-
-## Finished Items