From: Chris Mason <mason@suse.com>
To: Jakob Borg <jakob@borg.pp.se>, linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: More information on reiserfs bug
Date: Tue, 16 Jan 2001 14:12:23 -0500 [thread overview]
Message-ID: <208780000.979672343@tiny> (raw)
In-Reply-To: <20010116193858.A733@borg.pp.se>
On Tuesday, January 16, 2001 07:38:58 PM +0100 Jakob Borg
<jakob@borg.pp.se> wrote:
> Hi again,
>
> It seems the problem occurs every time i start fetchmail... Attached are
> ksymoops output and .config (if i remember this time). If there is
> anything else I can do to help debug this, just tell me
Linus fixed that hunk of debugging code in his merge, and it found a bug in
the reiserfs O_SYNC support. reiserfs_commit_write needs to hold the BKL.
This should fix it:
--- linux/fs/reiserfs/inode.c.1 Tue Jan 16 13:46:35 2001
+++ linux/fs/reiserfs/inode.c Tue Jan 16 13:49:21 2001
@@ -1853,6 +1853,11 @@
struct reiserfs_transaction_handle th ;
reiserfs_wait_on_write_block(inode->i_sb) ;
+
+ /* prevent_flush_page_lock must be called before generic_commit_write,
+ ** and the BKL must be held during the call.
+ */
+ lock_kernel() ;
prevent_flush_page_lock(page, inode) ;
ret = generic_commit_write(f, page, from, to) ;
/* we test for O_SYNC here so we can commit the transaction
@@ -1866,6 +1871,8 @@
journal_end_sync(&th, inode->i_sb, 1) ;
}
allow_flush_page_lock(page, inode) ;
+ unlock_kernel() ;
+
return ret ;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-16 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 18:38 More information on reiserfs bug Jakob Borg
2001-01-16 19:12 ` 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=208780000.979672343@tiny \
--to=mason@suse.com \
--cc=jakob@borg.pp.se \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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