From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deprecate use of bdflush()
Date: 02 Dec 2002 17:26:32 -0500 [thread overview]
Message-ID: <1038867991.1221.56.camel@phantasy> (raw)
In-Reply-To: <3DEBDA8D.CBB4B6D0@digeo.com>
On Mon, 2002-12-02 at 17:11, Andrew Morton wrote:
> 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.
Good idea.
I could do without the rate limiting, though - the print is after the
CAP_SYS_ADMIN check. Root has plenty of other ways to print crap to the
screen and it saves 32-bits from bss. But, uh, not a big deal at all
either way.
Robert Love
fs/buffer.c | 7 +++++++
1 files changed, 7 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 17:24:57.000000000 -0500
@@ -2757,11 +2757,18 @@
/*
* 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: process `%s' used the deprecated bdflush"
+ " system call. Fix your initscripts?\n",
+ current->comm);
if (func == 1)
do_exit(0);
return 0;
next prev parent reply other threads:[~2002-12-02 22:18 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
2002-12-02 22:26 ` Robert Love [this message]
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=1038867991.1221.56.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox