From: Jan Kara <jack@suse.cz>
To: Vladimir Saveliev <vs@namesys.com>
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 16:06:33 +0100 [thread overview]
Message-ID: <20050127150632.GA17882@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <1106835321.6191.130.camel@tribesman>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi!
> 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.
So in that case reiserfs_quota_read() also needs a BKL
because it can be called from the quota code without any lock
guarantees (e.g. quota_on() and quotactl() can call reading routine
without BKL).
Attached patch adds this BKL locking and adds also missing
lock_buffer() I found.
If you agree with the patch then you can forward it to Andrew/Linus.
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
[-- Attachment #2: reiser-lock-fix.diff --]
[-- Type: text/plain, Size: 1034 bytes --]
Add missing locking to reiserfs_quota_read() and reiserfs_quota_write().
Signed-off-by: Jan Kara <jack@suse.cz>
--- linux/fs/reiserfs/super.c 2005-01-27 12:56:27.000000000 +0100
+++ linux/fs/reiserfs/super.c 2005-01-27 17:41:20.000000000 +0100
@@ -1993,7 +1993,9 @@ static ssize_t reiserfs_quota_read(struc
tocopy = sb->s_blocksize - offset < toread ? sb->s_blocksize - offset : toread;
tmp_bh.b_state = 0;
/* Quota files are without tails so we can safely use this function */
+ reiserfs_write_lock(sb);
err = reiserfs_get_block(inode, blk, &tmp_bh, 0);
+ reiserfs_write_unlock(sb);
if (err)
return err;
if (!buffer_mapped(&tmp_bh)) /* A hole? */
@@ -2041,8 +2043,11 @@ static ssize_t reiserfs_quota_write(stru
err = -EIO;
goto out;
}
+ lock_buffer(bh);
memcpy(bh->b_data+offset, data, tocopy);
+ flush_dcache_page(bh->b_page);
set_buffer_uptodate(bh);
+ unlock_buffer(bh);
reiserfs_prepare_for_journal(sb, bh, 1);
journal_mark_dirty(current->journal_info, sb, bh);
if (!journal_quota)
next prev parent reply other threads:[~2005-01-27 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 7:24 Sergey S. Kostyliov
2005-01-27 10:17 ` Vladimir Saveliev
2005-01-27 11:26 ` Jan Kara
2005-01-27 14:15 ` Vladimir Saveliev
2005-01-27 15:06 ` Jan Kara [this message]
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=20050127150632.GA17882@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@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
all inboxes | Powered by JetHome®