From: Robert Love <rml@tech9.net>
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] deprecate use of bdflush()
Date: 02 Dec 2002 16:21:07 -0500 [thread overview]
Message-ID: <1038864066.1221.43.camel@phantasy> (raw)
We can never get rid of it if we do not deprecate it - so do so and
print a stern warning to those who still run bdflush daemons.
Patch is against 2.5.49-mm2. Please apply.
Robert Love
fs/buffer.c | 6 ++++++
1 files changed, 6 insertions(+)
diff -urN linux-2.5.49-mm2/fs/buffer.c linux/fs/buffer.c
--- linux-2.5.49-mm2/fs/buffer.c 2002-12-02 16:07:53.000000000 -0500
+++ linux/fs/buffer.c 2002-12-02 16:17:16.000000000 -0500
@@ -2757,11 +2757,17 @@
/*
* There are no bdflush tunables left. But distributions are
* still running obsolete flush daemons, so we terminate them here.
+ *
+ * Use of bdflush() is deprecated and will be removed in a future kernel.
+ * The `pdflush' kernel threads fully replace bdflush daemons and this call.
*/
asmlinkage long sys_bdflush(int func, long data)
{
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
+
+ printk(KERN_WARNING "warning: the bdflush system call is deprecated "
+ "and no longer needed. Stop using it.\n");
if (func == 1)
do_exit(0);
return 0;
next reply other threads:[~2002-12-02 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 21:21 Robert Love [this message]
2002-12-02 22:11 ` [PATCH] deprecate use of bdflush() Andrew Morton
2002-12-02 22:26 ` Robert Love
2002-12-03 14:24 ` Bill Davidsen
2002-12-03 17:10 ` Robert Love
2002-12-03 19:05 ` Paul Gortmaker
2002-12-04 1:12 ` Krzysztof Halasa
2002-12-04 16:11 ` Robert Love
2002-12-04 13:10 ` Daniel Kobras
2002-12-04 16:12 ` Robert Love
2002-12-04 19:29 ` Daniel Kobras
2002-12-05 17:39 ` Bill Davidsen
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=1038864066.1221.43.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.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 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.