From: Edward Shishkin <edward.shishkin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: [patch 3/7] roll back vfs-add-super_operationssync_inodes-2.patch
Date: Tue, 2 Feb 2010 02:56:15 +0100 [thread overview]
Message-ID: <201002020256.15908.edward.shishkin@gmail.com> (raw)
Roll back reiser4-vfs-add-super_operationssync_inodes-2.patch
(wrong stuff)
Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
fs/fs-writeback.c | 5 +----
include/linux/fs.h | 2 --
2 files changed, 1 insertion(+), 6 deletions(-)
Index: linux-2.6.33-rc5-mm1/fs/fs-writeback.c
===================================================================
--- linux-2.6.33-rc5-mm1.orig/fs/fs-writeback.c
+++ linux-2.6.33-rc5-mm1/fs/fs-writeback.c
@@ -1217,10 +1217,7 @@ EXPORT_SYMBOL(writeback_inodes_sb_if_idl
*/
void sync_inodes_sb(struct super_block *sb)
{
- if (sb->s_op->sync_inodes)
- sb->s_op->sync_inodes(sb, NULL);
- else
- bdi_sync_writeback(sb->s_bdi, sb);
+ bdi_sync_writeback(sb->s_bdi, sb);
wait_sb_inodes(sb);
}
EXPORT_SYMBOL(sync_inodes_sb);
Index: linux-2.6.33-rc5-mm1/include/linux/fs.h
===================================================================
--- linux-2.6.33-rc5-mm1.orig/include/linux/fs.h
+++ linux-2.6.33-rc5-mm1/include/linux/fs.h
@@ -1566,8 +1566,6 @@ struct super_operations {
void (*clear_inode) (struct inode *);
void (*umount_begin) (struct super_block *);
- void (*sync_inodes)(struct super_block *sb,
- struct writeback_control *wbc);
int (*show_options)(struct seq_file *, struct vfsmount *);
int (*show_stats)(struct seq_file *, struct vfsmount *);
#ifdef CONFIG_QUOTA
next reply other threads:[~2010-02-02 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 1:56 Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 15:24 [patch 3/7] roll back vfs-add-super_operationssync_inodes-2.patch Edward Shishkin
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=201002020256.15908.edward.shishkin@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=reiserfs-devel@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.