public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Jean Charles Delepine <delepine@u-picardie.fr>,
	linux-kernel@vger.kernel.org, alan@redhat.com, viro@math.psu.edu
Cc: linux-scsi@vger.kernel.org
Subject: Re: BUG in reiserfs with 2.4.2-ac20 + linux-aic7xxx Rev 6.1.7
Date: Mon, 26 Mar 2001 11:26:35 -0500	[thread overview]
Message-ID: <42730000.985623995@tiny> (raw)
In-Reply-To: <m2n1a826ri.fsf@eloi.machoro.ka>



> 
> Mar 25 06:56:50 gip2 kernel: journal_begin called without kernel lock held
> Mar 25 06:56:50 gip2 kernel: kernel BUG at journal.c:423!
> 
Ok, this BUG is there to catch people trying to use the reiserfs journal
without the BKL held.  Older ac series kernel had a bug where vmtruncate
would trigger this when called from generic_file_write (which your stack
trace shows you hit).

But, ac20 should have the fix.  Looks like only the expanding truncate case
ended up under the BKL in vmtruncate.  This untested diff is stolen from the
expanding truncate fix in ac25:

--- linux/mm/memory.c.1	Mon Mar 26 11:05:25 2001
+++ linux/mm/memory.c	Mon Mar 26 11:06:31 2001
@@ -969,7 +969,12 @@
 	spin_unlock(&mapping->i_shared_lock);
 	truncate_inode_pages(mapping, offset);
 	if (inode->i_op && inode->i_op->truncate)
+	{
+		/* This doesnt scale but it is meant to be a 2.4 invariant */
+		lock_kernel();
 		inode->i_op->truncate(inode);
+		unlock_kernel();
+	}
 	return 0;
 
 do_expand:

-chris


      reply	other threads:[~2001-03-26 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26  9:56 BUG in reiserfs with 2.4.2-ac20 + linux-aic7xxx Rev 6.1.7 Jean Charles Delepine
2001-03-26 16:26 ` Chris Mason [this message]

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=42730000.985623995@tiny \
    --to=mason@suse.com \
    --cc=alan@redhat.com \
    --cc=delepine@u-picardie.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox