public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Saveliev <vs@namesys.com>
To: Jan Kara <jack@suse.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.11-rc2] kernel BUG at fs/reiserfs/prints.c:362
Date: Thu, 27 Jan 2005 17:15:22 +0300	[thread overview]
Message-ID: <1106835321.6191.130.camel@tribesman> (raw)
In-Reply-To: <20050127112647.GA20806@atrey.karlin.mff.cuni.cz>

Hello

On Thu, 2005-01-27 at 14:26, Jan Kara wrote:
>   Hello,
> 
> > On Thu, 2005-01-27 at 10:24, Sergey S. Kostyliov wrote:
> > > Hello all,
> > > 
> > > Here is a BUG() I've just hited on quota enabled reiserfs disk.
> > > 
> > > rathamahata@dev rathamahata $ mount | grep /dev/sdb2
> > > /dev/sdb2 on /var/www type reiserfs (rw,noatime,nodiratime,data=writeback,grpquota,usrquota)
> > > rathamahata@dev rathamahata $
> > > 
> > > REISERFS: panic (device sdb2): journal_begin called without kernel lock held
> > 
> > Would you check whether this patch helps, please?
>   BTW: What are the exact rules where lock_kernel() should be held for
> reiserfs? Is there a doc somewhere? 
I do not think so.
Earlier reiserfs used to lock_kernel on entering and unlock on exit. The
reason is that reiserfs has no fine grain locking protecting access to
its data structures.
Since that time there could be introduced some minor improvements,
though.

> I suspect we might need the lock
> also for reiserfs_quota_read() (reiserfs_quota_write() should be
> already protected by your fix).
>   Hmm, I should also check ext2/ext3 whether it needs the lock...
> 
> 								Honza


  reply	other threads:[~2005-01-27 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27  7:24 [2.6.11-rc2] kernel BUG at fs/reiserfs/prints.c:362 Sergey S. Kostyliov
2005-01-27 10:17 ` Vladimir Saveliev
2005-01-27 11:26   ` Jan Kara
2005-01-27 14:15     ` Vladimir Saveliev [this message]
2005-01-27 15:06       ` Jan Kara
2005-01-28 21:53       ` Lee Revell
2005-01-27 12:52   ` Sergey S. Kostyliov

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=1106835321.6191.130.camel@tribesman \
    --to=vs@namesys.com \
    --cc=jack@suse.cz \
    --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