From: Jan Kara <jack@suse.cz>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/7] affs: stop using lock_super
Date: Wed, 6 Jun 2012 12:07:58 +0200 [thread overview]
Message-ID: <20120606100758.GB6304@quack.suse.cz> (raw)
In-Reply-To: <1338895695-10362-6-git-send-email-dedekind1@gmail.com>
On Tue 05-06-12 14:28:13, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
> The VFS's 'lock_super()' and 'unlock_super()' calls are deprecated and unwanted
> and just wait for a brave knight who'd kill them. This patch makes AFFS stop
> using them and introduces own AFFS superblock mutex which we use for
> serializeing the root block changes.
Hum, why not just use the buffer lock for this?
Honza
>
> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> ---
> fs/affs/affs.h | 1 +
> fs/affs/super.c | 5 +++--
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/affs/affs.h b/fs/affs/affs.h
> index 45a0ce4..b8af745 100644
> --- a/fs/affs/affs.h
> +++ b/fs/affs/affs.h
> @@ -108,6 +108,7 @@ struct affs_sb_info {
> char *s_prefix; /* Prefix for volumes and assigns. */
> char s_volume[32]; /* Volume prefix for absolute symlinks. */
> spinlock_t symlink_lock; /* protects the previous two */
> + struct mutex s_lock; /* protects the SB's buffer-head */
> };
>
> #define SF_INTL 0x0001 /* International filesystem. */
> diff --git a/fs/affs/super.c b/fs/affs/super.c
> index 8293cb9..8674915 100644
> --- a/fs/affs/super.c
> +++ b/fs/affs/super.c
> @@ -31,14 +31,14 @@ affs_commit_super(struct super_block *sb, int wait)
> struct buffer_head *bh = sbi->s_root_bh;
> struct affs_root_tail *tail = AFFS_ROOT_TAIL(sb, bh);
>
> - lock_super(sb);
> + mutex_lock(&sbi->s_lock);
> tail->bm_flag = cpu_to_be32(2);
> secs_to_datestamp(get_seconds(), &tail->disk_change);
> affs_fix_checksum(sb, bh);
> mark_buffer_dirty(bh);
> if (wait)
> sync_dirty_buffer(bh);
> - unlock_super(sb);
> + mutex_unlock(&sbi->s_lock);
> }
>
> static void
> @@ -299,6 +299,7 @@ static int affs_fill_super(struct super_block *sb, void *data, int silent)
> return -ENOMEM;
>
> sb->s_fs_info = sbi;
> + mutex_init(&sbi->s_lock);
> mutex_init(&sbi->s_bmlock);
> spin_lock_init(&sbi->symlink_lock);
>
> --
> 1.7.7.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-06-06 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 11:28 [PATCH 0/7] affs: stop using write_supers and s_dirt Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 1/7] affs: remove strange argument of affs_commit_super Artem Bityutskiy
2012-06-06 10:29 ` Jan Kara
2012-06-05 11:28 ` [PATCH 2/7] affs: remove useless superblock writeout on unmount Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 3/7] affs: remove useless superblock writeout on remount Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 4/7] affs: re-structure superblock locking a bit Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 5/7] affs: stop using lock_super Artem Bityutskiy
2012-06-06 10:07 ` Jan Kara [this message]
2012-06-06 16:00 ` Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 6/7] affs: introduce VFS superblock object back-reference Artem Bityutskiy
2012-06-05 11:28 ` [PATCH 7/7] affs: get rid of affs_sync_super Artem Bityutskiy
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=20120606100758.GB6304@quack.suse.cz \
--to=jack@suse.cz \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).