From: Chris Mason <mason@suse.com>
To: Tigran Aivazian <tigran@veritas.com>, Hans Reiser <hans@reiser.to>
Cc: linux-kernel@vger.kernel.org
Subject: Re: panic in reiserfs: _get_block_create_0 gets bh_result->b_data = NULL
Date: Wed, 08 Nov 2000 17:50:40 -0500 [thread overview]
Message-ID: <202710000.973723840@coffee> (raw)
In-Reply-To: <Pine.LNX.4.21.0011031556120.1019-100000@saturn.homenet>
On Friday, November 03, 2000 15:56:36 +0000 Tigran Aivazian <tigran@veritas.com> wrote:
> On Fri, 3 Nov 2000, Tigran Aivazian wrote:
>
>> Hi Hans,
>>
>> Simply starting the validation phase of SPEC SFS with NFS mounted reiserfs
>> filesystem panics as shown in the log below. A quick look at the source
>> suggests that _get_block_create_0() (and therefore, more generally,
>> reiserfs_get_block()) was passed a buffer head bh_result with ->b_data =
>> NULL. So, we panic at line 256 of fs/reiserfs/inode.c when doing:
>>
>> memset (bh_result->b_data, 0, inode->i_sb->s_blocksize)
>>
>
Ok, I've tracked these down to a few places in our tail handling code. Working on the fixes now.
-chris
-
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/
next prev parent reply other threads:[~2000-11-08 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 14:34 panic in reiserfs in 2.4.0-test10, BUG at highmem.c:220 Tigran Aivazian
2000-11-03 15:54 ` panic in reiserfs: _get_block_create_0 gets bh_result->b_data = NULL Tigran Aivazian
2000-11-03 15:56 ` Tigran Aivazian
2000-11-08 22:50 ` Chris Mason [this message]
2000-11-06 7:43 ` Hans Reiser
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=202710000.973723840@coffee \
--to=mason@suse.com \
--cc=hans@reiser.to \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.