From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: [FS] Why doesn't this patch work?
Date: Wed, 5 Dec 2001 15:28:34 -0800 [thread overview]
Message-ID: <20011205152834.A11289@netnation.com> (raw)
I'm attempting to write this little dinky patch to see who calls fsync()
or fdatasync(), but it's spitting out compiler warnings. I can't figure
out why, though. What did I do wrong?
buffer.c: In function `report_culprit':
buffer.c:409: warning: assignment from incompatible pointer type
buffer.c:410: warning: passing arg 2 of `d_path' from incompatible pointer type
buffer.c:420: warning: passing arg 1 of `mntput' from incompatible pointer type
--- linux/fs/buffer.c.orig Wed Dec 5 08:53:28 2001
+++ linux/fs/buffer.c Wed Dec 5 15:14:38 2001
@@ -396,6 +396,30 @@
return ret;
}
+static void report_culprit(struct dentry *dentry, struct file *file, char *action)
+{
+ struct vfsmnt * mnt;
+ char * buf = (char*)__get_free_page(GFP_KERNEL);
+ char * path;
+ int len;
+
+ if (!buf)
+ return;
+
+ mnt = mntget(file->f_vfsmnt);
+ path = d_path(dentry, mnt, buf, PAGE_SIZE - 1);
+ len = buf + PAGE_SIZE - 1 - path;
+ if (len >= PAGE_SIZE - 1)
+ len = PAGE_SIZE - 1;
+ path[len] = '\0';
+
+ printk("Process %u (%s) %s()ed \"%s\".\n",
+ current->pid, current->comm, action, path);
+
+ free_page((unsigned long)buf);
+ mntput(mnt);
+}
+
asmlinkage long sys_fsync(unsigned int fd)
{
struct file * file;
@@ -415,6 +439,8 @@
if (!file->f_op || !file->f_op->fsync)
goto out_putf;
+ report_culprit(dentry, file, "fsync");
+
/* We need to protect against concurrent writers.. */
down(&inode->i_sem);
filemap_fdatasync(inode->i_mapping);
@@ -446,6 +472,8 @@
err = -EINVAL;
if (!file->f_op || !file->f_op->fsync)
goto out_putf;
+
+ report_culprit(dentry, file, "fdatasync");
down(&inode->i_sem);
filemap_fdatasync(inode->i_mapping);
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
next reply other threads:[~2001-12-05 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 23:28 Simon Kirby [this message]
2001-12-05 23:46 ` [FS] Why doesn't this patch work? Robert Love
2001-12-06 0:08 ` Simon Kirby
2001-12-05 23:52 ` Dave Jones
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=20011205152834.A11289@netnation.com \
--to=sim@netnation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.