From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.6] reiserfs: fix locking in reiserfs_remount
Date: Thu, 7 Aug 2003 17:33:58 +0400 [thread overview]
Message-ID: <20030807133358.GC20639@namesys.com> (raw)
In-Reply-To: <3F32531B.7080000@namesys.com>
Hello!
On Thu, Aug 07, 2003 at 05:24:43PM +0400, Hans Reiser wrote:
> >Reiserfs needs BKL for it's journal operations. This is not "more",
> >for some time BKL was taken in the VFS, then whoever removed that,
> >forgot to propagate BKL down to actual fs methods that need the BKL.
> Is it known who removed it?
I think it was Andrew. At least this new emergency remount path without
BKL was introduced by his patch without any extra attribution.
Bye,
Oleg
next prev parent reply other threads:[~2003-08-07 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 9:38 [PATCH] [2.6] reiserfs: fix locking in reiserfs_remount Oleg Drokin
2003-08-06 17:28 ` Mike Fedyk
2003-08-06 17:31 ` Oleg Drokin
2003-08-07 13:24 ` Hans Reiser
2003-08-07 13:33 ` Oleg Drokin [this message]
2003-08-07 15:24 ` Andrew Morton
2003-08-07 15:27 ` Oleg Drokin
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=20030807133358.GC20639@namesys.com \
--to=green@namesys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/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).