From: Andrew Morton <akpm@linux-foundation.org>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: jblunck@suse.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, matthew@wil.cx,
viro@zeniv.linux.org.uk
Subject: Re: BKL: Remove BKL from Squashfs
Date: Tue, 10 Nov 2009 12:15:11 -0800 [thread overview]
Message-ID: <20091110121511.5adca8a9.akpm@linux-foundation.org> (raw)
In-Reply-To: <E1N5L6K-0008LW-6y@dylan.lougher.demon.co.uk>
On Tue, 03 Nov 2009 15:15:16 +0000
Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
>
> BKL is only used in fill_super/put_super. It is safe to remove it.
>
What kernel are you trying to patch here?
Most of your patch is already present in mainline. Against mainline,
this what is left of your patch:
--- a/fs/squashfs/super.c~bkl-remove-bkl-from-squashfs
+++ a/fs/squashfs/super.c
@@ -30,7 +30,6 @@
#include <linux/fs.h>
#include <linux/vfs.h>
#include <linux/slab.h>
-#include <linux/smp_lock.h>
#include <linux/mutex.h>
#include <linux/pagemap.h>
#include <linux/init.h>
@@ -339,8 +338,6 @@ static int squashfs_remount(struct super
static void squashfs_put_super(struct super_block *sb)
{
- lock_kernel();
-
if (sb->s_fs_info) {
struct squashfs_sb_info *sbi = sb->s_fs_info;
squashfs_cache_delete(sbi->block_cache);
@@ -353,8 +350,6 @@ static void squashfs_put_super(struct su
kfree(sb->s_fs_info);
sb->s_fs_info = NULL;
}
-
- unlock_kernel();
}
So someone has decided to remove lots of lock_kernel()'s but chose to
leave the squashfs_put_super() ones behind.
Why did they do that? Your patch effectively asserts that their
decision was incorrect.
So please rethink, update the changelog appropriately and resend.
next prev parent reply other threads:[~2009-11-10 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:15 BKL: Remove BKL from Squashfs Phillip Lougher
2009-11-10 20:15 ` Andrew Morton [this message]
2009-11-10 21:11 ` Phillip Lougher
2009-11-10 21:37 ` Phillip Lougher
2009-11-11 15:16 ` Jan Blunck
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=20091110121511.5adca8a9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=phillip@lougher.demon.co.uk \
--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).