From: Boaz Harrosh <bharrosh@panasas.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: <bhalevy@tonian.com>, <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
<adilger.kernel@dilger.ca>, <tytso@mit.edu>,
<hirofumi@mail.parknet.co.jp>, <mikulas@artax.karlin.mff.cuni.cz>,
Al Viro <viro@ZenIV.linux.org.uk>, <hch@infradead.org>,
<dushistov@mail.ru>, <osd-dev@open-osd.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
<linux-ext4@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/8] vfs: remove lock and unlock functions for super block
Date: Thu, 16 Aug 2012 15:26:40 +0300 [thread overview]
Message-ID: <502CE700.3070709@panasas.com> (raw)
In-Reply-To: <502CC499.4030109@gmail.com>
On 08/16/2012 12:59 PM, Marco Stornelli wrote:
> From: Marco Stornelli <marco.stornelli@gmail.com>
>
> Remove lock_super and unlock_super from VFS.
>
> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
You can't remove the lock here. After this patch the tree will
not compile, and will not be bisectable. You must move this patch
to be last.
Each patch should leave the tree compileable and with out any
regressions.
Boaz
> ---
>
> diff -Nurp linux-3.6-rc1-orig/fs/super.c linux-3.6-rc1/fs/super.c
> --- linux-3.6-rc1-orig/fs/super.c 2012-08-16 09:37:35.000000000 +0200
> +++ linux-3.6-rc1/fs/super.c 2012-08-16 09:43:46.000000000 +0200
> @@ -186,15 +186,8 @@ static struct super_block *alloc_super(s
> spin_lock_init(&s->s_inode_lru_lock);
> INIT_LIST_HEAD(&s->s_mounts);
> init_rwsem(&s->s_umount);
> - mutex_init(&s->s_lock);
> lockdep_set_class(&s->s_umount, &type->s_umount_key);
> /*
> - * The locking rules for s_lock are up to the
> - * filesystem. For example ext3fs has different
> - * lock ordering than usbfs:
> - */
> - lockdep_set_class(&s->s_lock, &type->s_lock_key);
> - /*
> * sget() can have s_umount recursion.
> *
> * When it cannot find a suitable sb, it allocates a new
> @@ -400,22 +393,6 @@ bool grab_super_passive(struct super_blo
> return false;
> }
> -/*
> - * Superblock locking. We really ought to get rid of these two.
> - */
> -void lock_super(struct super_block * sb)
> -{
> - mutex_lock(&sb->s_lock);
> -}
> -
> -void unlock_super(struct super_block * sb)
> -{
> - mutex_unlock(&sb->s_lock);
> -}
> -
> -EXPORT_SYMBOL(lock_super);
> -EXPORT_SYMBOL(unlock_super);
> -
> /**
> * generic_shutdown_super - common helper for ->kill_sb()
> * @sb: superblock to kill
>
> diff -Nurp linux-3.6-rc1-orig/include/linux/fs.h linux-3.6-rc1/include/linux/fs.h
> --- linux-3.6-rc1-orig/include/linux/fs.h 2012-08-16 11:38:42.000000000 +0200
> +++ linux-3.6-rc1/include/linux/fs.h 2012-08-16 09:45:18.000000000 +0200
> @@ -1504,7 +1504,6 @@ struct super_block {
> unsigned long s_magic;
> struct dentry *s_root;
> struct rw_semaphore s_umount;
> - struct mutex s_lock;
> int s_count;
> atomic_t s_active;
> #ifdef CONFIG_SECURITY
next prev parent reply other threads:[~2012-08-16 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 9:59 [PATCH 1/8] vfs: remove lock and unlock functions for super block Marco Stornelli
2012-08-16 12:26 ` Boaz Harrosh [this message]
2012-08-16 16:05 ` Marco Stornelli
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=502CE700.3070709@panasas.com \
--to=bharrosh@panasas.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@tonian.com \
--cc=dushistov@mail.ru \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=osd-dev@open-osd.org \
--cc=tytso@mit.edu \
--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 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.