From: Matthew Wilcox <willy@debian.org>
To: Paul Menage <pmenage@ensim.com>
Cc: Alexander Viro <viro@math.psu.edu>,
torvalds@transmeta.com, linux-fsdevel@ensim.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shift BKL into ->statfs()
Date: Wed, 3 Jul 2002 13:28:48 +0100 [thread overview]
Message-ID: <20020703132848.M27706@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <E17Pf1Q-0004ip-00@pmenage-dt.ensim.com>; from pmenage@ensim.com on Wed, Jul 03, 2002 at 12:57:56AM -0700
On Wed, Jul 03, 2002 at 12:57:56AM -0700, Paul Menage wrote:
> All ->statfs() implementations have been modified to take the BKL,
> except for the following:
>
> - those that don't reference any external mutable data:
... also adfs_statfs,
> - those that already have their own locking:
... also affs_statfs, bfs_statfs, ext3_statfs, hfs_statfs, jffs2_statfs,
jfs_statfs
I think ufs_statfs needs lock_super() due to its handling of fragments.
qnx4 looks terribly broken for read-write anyway... probably just keep the
lock_kernel / unlock_kernel around the call to qnx4_count_free_blocks().
I haven't audited coda, hpfs, jffs, nfs, smbfs & udf.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-07-03 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 1:25 [PATCH] Shift BKL into ->statfs() Paul Menage
2002-07-03 2:57 ` Matthew Wilcox
2002-07-03 3:04 ` Paul Menage
2002-07-03 6:07 ` Alexander Viro
2002-07-03 6:25 ` Alexander Viro
2002-07-03 7:57 ` Paul Menage
2002-07-03 12:28 ` Matthew Wilcox [this message]
2002-07-03 12:28 ` Matthew Wilcox
2002-07-03 9:55 ` Oleg Drokin
2002-07-03 10:34 ` Anton Altaparmakov
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=20020703132848.M27706@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-fsdevel@ensim.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenage@ensim.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.