From: Paul Menage <menage@google.com>
To: Jan Blunck <jblunck@suse.de>
Cc: linux-fsdevel@vger.kernel.org,
Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
jkacur@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
matthew@wil.cx, Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 17/20] BKL: Remove BKL from cgroup
Date: Wed, 18 Nov 2009 10:24:30 -0800 [thread overview]
Message-ID: <6599ad830911181024l5a4d534cs608409f1d42eed26@mail.gmail.com> (raw)
In-Reply-To: <1258536293-7762-18-git-send-email-jblunck@suse.de>
On Wed, Nov 18, 2009 at 1:24 AM, Jan Blunck <jblunck@suse.de> wrote:
> The BKL is only used in remount_fs and get_sb that are both protected by
> the superblocks s_umount rw_semaphore. Therefore it is safe to remove the
> BKL entirely.
>
> Signed-off-by: Jan Blunck <jblunck@suse.de>
Acked-by: Paul Menage <menage@google.com>
next prev parent reply other threads:[~2009-11-18 18:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 9:24 [PATCH 00/20] BKL pushdown from do_new_mount() to the filesystems (v3) Jan Blunck
2009-11-18 9:24 ` [PATCH 01/20] JFS: Free sbi memory in error path Jan Blunck
2009-11-18 9:24 ` [PATCH 02/20] AFFS: " Jan Blunck
2009-11-18 9:24 ` [PATCH 04/20] BKL: Remove outdated comment and include Jan Blunck
2009-11-18 9:24 ` [PATCH 05/20] BKL: Remove BKL from Amiga FFS Jan Blunck
2009-11-18 9:24 ` [PATCH 06/20] BKL: Remove BKL from BFS Jan Blunck
2009-11-18 9:24 ` [PATCH 07/20] BKL: Remove BKL from CifsFS Jan Blunck
2009-11-18 9:24 ` [PATCH 08/20] BKL: Remove BKL from ext3 fill_super() Jan Blunck
2009-11-18 9:24 ` [PATCH 09/20] BKL: Remove BKL from ext3_put_super() and ext3_remount() Jan Blunck
2009-11-18 9:24 ` [PATCH 10/20] BKL: Remove BKL from ext4 filesystem Jan Blunck
2009-11-18 9:24 ` [PATCH 11/20] BKL: Remove BKL from exofs Jan Blunck
2009-11-18 9:24 ` [PATCH 12/20] BKL: Remove BKL from HFS Jan Blunck
2009-11-18 9:24 ` [PATCH 13/20] BKL: Remove BKL from HFS+ Jan Blunck
2009-11-18 9:24 ` [PATCH 14/20] BKL: Remove BKL from JFS Jan Blunck
2009-11-18 9:24 ` [PATCH 15/20] BKL: Remove BKL from NILFS2 Jan Blunck
2009-11-18 14:40 ` Ryusuke Konishi
2009-11-18 9:24 ` [PATCH 16/20] BKL: Remove BKL from NTFS Jan Blunck
2009-11-18 9:24 ` [PATCH 17/20] BKL: Remove BKL from cgroup Jan Blunck
2009-11-18 18:24 ` Paul Menage [this message]
2009-11-18 9:24 ` [PATCH 18/20] BKL: Remove BKL from do_new_mount() Jan Blunck
2009-11-18 9:24 ` [PATCH 19/20] ext2: Add ext2_sb_info s_lock spinlock Jan Blunck
2009-11-18 12:31 ` OGAWA Hirofumi
2009-11-18 9:24 ` [PATCH 20/20] BKL: Remove BKL from ext2 filesystem Jan Blunck
[not found] ` <1258536293-7762-4-git-send-email-jblunck@suse.de>
2009-11-18 10:41 ` [PATCH 03/20] BKL: Explicitly add BKL around get_sb/fill_super Anders Larsen
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=6599ad830911181024l5a4d534cs608409f1d42eed26@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthew@wil.cx \
--cc=tglx@linutronix.de \
/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).