From: Andrew Morton <akpm@digeo.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deprecate use of bdflush()
Date: Mon, 02 Dec 2002 14:11:25 -0800 [thread overview]
Message-ID: <3DEBDA8D.CBB4B6D0@digeo.com> (raw)
In-Reply-To: 1038864066.1221.43.camel@phantasy
Robert Love wrote:
>
> 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.
>
Ho-hum. I was going to do this months ago but general exhaustion
and sluggishness won out.
We should tell the user which process called sys_bdflush() to aid
their expunging efforts.
--- 25/fs/buffer.c~deprecate-bdflush Mon Dec 2 13:40:44 2002
+++ 25-akpm/fs/buffer.c Mon Dec 2 13:45:11 2002
@@ -2755,11 +2755,25 @@ int block_sync_page(struct page *page)
/*
* 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)
{
+ static int msg_count;
+
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
+
+ if (msg_count < 5) {
+ msg_count++;
+ printk(KERN_INFO
+ "warning: process `%s' used the obsolete bdflush"
+ " system call\nFix your initscripts?\n",
+ current->comm);
+ }
+
if (func == 1)
do_exit(0);
return 0;
_
next prev parent reply other threads:[~2002-12-02 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 21:21 [PATCH] deprecate use of bdflush() Robert Love
2002-12-02 22:11 ` Andrew Morton [this message]
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=3DEBDA8D.CBB4B6D0@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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;
as well as URLs for NNTP newsgroup(s).