linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.6] reiserfs: fix locking in reiserfs_remount
Date: Thu, 07 Aug 2003 17:24:43 +0400	[thread overview]
Message-ID: <3F32531B.7080000@namesys.com> (raw)
In-Reply-To: <20030806173114.GB15024@namesys.com>

Oleg Drokin wrote:

>Hello!
>
>On Wed, Aug 06, 2003 at 10:28:13AM -0700, Mike Fedyk wrote:
>  
>
>>>    Since reiserfs_remount can be called without BKL held, we better take BKL in there.
>>>    Please apply the below patch. It is against 2.6.0-test2
>>>      
>>>
>>is the BKL in reiserfs_write_unlock()?
>>    
>>
>
>Yes.
>
>  
>
>>Do we need to be adding more BKL usage, instead of the same or less at this
>>point?
>>    
>>
>
>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.
>
>Bye,
>    Oleg
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>
Is it known who removed it?

-- 
Hans



  reply	other threads:[~2003-08-07 13:24 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 [this message]
2003-08-07 13:33       ` Oleg Drokin
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=3F32531B.7080000@namesys.com \
    --to=reiser@namesys.com \
    --cc=akpm@osdl.org \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).