From: sashiko-bot@kernel.org
To: "David Howells" <dhowells@redhat.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH] cachefiles,netfs: sunset ondemand mode
Date: Wed, 12 Aug 2026 15:07:27 +0000 [thread overview]
Message-ID: <20260812150727.832781F000E9@smtp.kernel.org> (raw)
In-Reply-To: <1046393.1786544127@warthog.procyon.org.uk>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Complete removal of the UAPI header include/uapi/linux/cachefiles.h breaks userspace compilation.
--
--- Patch [1]: [PATCH] cachefiles,netfs: sunset ondemand mode ---
commit e5845e932fdde67ddaf43301939e4efa8d4c2a07
Author: Gao Xiang <xiang@kernel.org>
cachefiles,netfs: sunset ondemand mode
This commit removes the ondemand read mode from cachefiles. Since EROFS over
fscache is now removed and netfs has evolved, the ondemand mode is no longer
needed and is being cleaned up.
Link: https://lore.kernel.org/r/CAOQ4uxi4dzxArY24YO=+kBCK2gGoq3Ptb8WkzCqSogPgU_R3dQ@mail.gmail.com
Link: https://sashiko.dev/#/patchset/20260716103030.3065561-1-dhowells%40redhat.com
Link: https://sashiko.dev/#/patchset/20260722130218.78958-1-dhowells%40redhat.com
[ ... ]
> diff --git a/include/uapi/linux/cachefiles.h b/include/uapi/linux/cachefiles.h
> deleted file mode 100644
> index 78caa73e53434..0000000000000
> --- a/include/uapi/linux/cachefiles.h
> +++ /dev/null
> @@ -1,68 +0,0 @@
> -/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> -#ifndef _LINUX_CACHEFILES_H
> -#define _LINUX_CACHEFILES_H
[Severity: High]
Does this complete removal of the UAPI header break userspace compilation?
Even when a kernel feature is sunset and its runtime support is removed,
standard Linux kernel policy is to retain the UAPI headers (or leave them
as stubs) to avoid breaking userspace source compilation. Any existing
userspace applications (such as ondemand cachefiles daemons) that include
linux/cachefiles.h will fail to build against the updated kernel headers.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/1046393.1786544127@warthog.procyon.org.uk?part=1
next prev parent reply other threads:[~2026-08-12 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 14:15 [PATCH] cachefiles,netfs: sunset ondemand mode David Howells
2026-08-12 14:26 ` Christian Brauner
2026-08-12 15:07 ` sashiko-bot [this message]
2026-08-12 15:10 ` bot+bpf-ci
-- strict thread matches above, loose matches on Subject: below --
2026-07-06 3:04 Gao Xiang
2026-07-07 18:59 ` Christian Brauner
2026-07-07 19:05 ` Gao Xiang
2026-07-17 9:27 ` David Howells
2026-07-17 9:39 ` Gao Xiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260812150727.832781F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.