From: Chris Mason <mason@suse.com>
From: Chris Mason <mason@suse.com>
To: akpm@osdl.org, linux-fsdevel@vger.kernel.org, reiserfs-list@namesys.com
Subject: [patch 2/6] reiserfs v3 patches
Subject: [patch 2/6] Zero b_private when allocating buffer heads
Date: Sun, 15 Jan 2006 19:50:04 -0500 [thread overview]
Message-ID: <20060116005312.206779000@watt.suse.com> (raw)
In-Reply-To: 20060116005002.398989000@watt.suse.com
[-- Attachment #1: b_private-init --]
[-- Type: text/plain, Size: 507 bytes --]
The b_private field in buffer heads needs to be zero filled
when the buffers are allocated. Thanks to Nathan Scott for
finding this. It was causing problems on systems with both XFS and
reiserfs.
diff -r 5ef1fa0a021a fs/buffer.c
--- a/fs/buffer.c Fri Jan 13 13:50:39 2006 -0500
+++ b/fs/buffer.c Fri Jan 13 13:51:09 2006 -0500
@@ -1022,6 +1022,7 @@ try_again:
bh->b_state = 0;
atomic_set(&bh->b_count, 0);
+ bh->b_private = NULL;
bh->b_size = size;
/* Link the buffer to its page */
--
next prev parent reply other threads:[~2006-01-16 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 0:50 [patch 0/6] reiserfs v3 patches Chris Mason
2006-01-16 0:50 ` [patch 1/6] reiserfs v3 patches, [patch 1/6] fix reiserfs_invalidatepage race against data=ordered Chris Mason, Chris Mason
2006-01-16 0:50 ` Chris Mason, Chris Mason [this message]
2006-01-16 0:50 ` [patch 3/6] reiserfs v3 patches, [patch 3/6] reiserfs hang and performance fix for data=journal mode Chris Mason, Chris Mason
2006-01-16 0:50 ` [patch 4/6] reiserfs v3 patches, [patch 4/6] reiserfs write_ordered_buffers should not oops on dirty non-uptodate bh Chris Mason, Chris Mason
2006-01-16 0:50 ` [patch 5/6] reiserfs v3 patches, [patch 5/6] reiserfs fix journal accounting in journal_transaction_should_end Chris Mason, Chris Mason
2006-01-16 0:50 ` [patch 6/6] reiserfs v3 patches, [patch 6/6] reiserfs: check for files > 2GB on 3.5.x disks Chris Mason, Jeff Mahoney
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=20060116005312.206779000@watt.suse.com \
--to=mason@suse.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-list@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;
as well as URLs for NNTP newsgroup(s).