From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Amir Goldstein <amir73il@gmail.com>,
Jani Nikula <jani.nikula@intel.com>,
Wei Liu <wei.liu@kernel.org>,
Joel Granados <joel.granados@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH] acct(2): begin the deprecation of legacy BSD process accounting
Date: Tue, 06 Jan 2026 09:38:22 -0500 [thread overview]
Message-ID: <20260106-bsd-acct-v1-1-d15564b52c83@kernel.org> (raw)
As Christian points out [1], even though it's privileged, this interface
has a lot of footguns. There are better options these days (e.g. eBPF),
so it would be good to start discouraging its use and mark it as
deprecated.
[1]: https://lore.kernel.org/linux-fsdevel/20250212-giert-spannend-8893f1eaba7d@brauner/
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
I meant to send this months ago, but never got around to it. Let's at
least mark this as deprecated and see who complains. We could also
consider adding a pr_warn_once() that fires the first time someone calls
acct(2) if we want to kill this in a more near-term timeframe.
---
init/Kconfig | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index fa79feb8fe57bb01d8ce8f35e33535709b57d452..160c1c4ef253593d62650cd5a53f3421bc9372d3 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -624,8 +624,9 @@ config SCHED_HW_PRESSURE
arch_update_hw_pressure() and arch_scale_thermal_pressure().
config BSD_PROCESS_ACCT
- bool "BSD Process Accounting"
+ bool "BSD Process Accounting (DEPRECATED)"
depends on MULTIUSER
+ default n
help
If you say Y here, a user level program will be able to instruct the
kernel (via a special system call) to write process accounting
@@ -635,7 +636,9 @@ config BSD_PROCESS_ACCT
command name, memory usage, controlling terminal etc. (the complete
list is in the struct acct in <file:include/linux/acct.h>). It is
up to the user level program to do useful things with this
- information. This is generally a good idea, so say Y.
+ information. This mechanism is antiquated and has significant
+ scalability issues. You probably want to use eBPF instead. Say
+ N unless you really need this.
config BSD_PROCESS_ACCT_V3
bool "BSD Process Accounting version 3 file format"
---
base-commit: 7f98ab9da046865d57c102fd3ca9669a29845f67
change-id: 20260106-bsd-acct-c60be8e6ae62
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-01-06 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 14:38 Jeff Layton [this message]
2026-01-12 10:06 ` Christian Brauner
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=20260106-bsd-acct-v1-1-d15564b52c83@kernel.org \
--to=jlayton@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jani.nikula@intel.com \
--cc=joel.granados@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wei.liu@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®