From: Hans Reiser <reiser@namesys.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
linux-xfs@oss.sgi.com, Jeff Mahoney <jeffm@suse.com>,
Mattia Dongili <malattia@linux.it>
Subject: Re: 2.6.15-mm3 bisection: git-xfs.patch makes reiserfs oops
Date: Mon, 16 Jan 2006 01:29:58 -0800 [thread overview]
Message-ID: <43CB6796.4040104@namesys.com> (raw)
In-Reply-To: <20060116094817.A8425113@wobbly.melbourne.sgi.com>
Thanks Nathan, Mattia, and Andrew.
vs, can you or Jeff look at whether our buffer head inits are
sufficiently hardened by next Monday (I know that vs has a lot of mail
to catch up to)? Jeff, if you have time before then, it would be nice
if you could handle it, I know hardening V3 is an interest of yours.
Thanks,
Hans
Nathan Scott wrote:
>On Sun, Jan 15, 2006 at 11:14:58PM +0100, Mattia Dongili wrote:
>
>
>>[CC-in relevant people/ML]
>>
>>Hello!
>>
>>second bisection result!
>>
>>On Tue, Jan 10, 2006 at 05:00:37PM -0800, Andrew Morton wrote:
>>
>>
>>>Mattia Dongili <malattia@linux.it> wrote:
>>>
>>>
>>[...]
>>
>>
>>>>1- reiser3 oopsed[1] twice while suspending to ram. It seems
>>>> reproducible (have some activity on the fs and suspend)
>>>>
>>>>
>>>No significant reiser3 changes in there, so I'd be suspecting something
>>>else has gone haywire.
>>>
>>>
>>you're right: git-xfs.patch is the bad guy.
>>
>>Unfortunately netconsole isn't helpful in capturing the oops (no serial
>>ports here) but I have two more shots (more readable):
>>http://oioio.altervista.org/linux/dsc03148.jpg
>>http://oioio.altervista.org/linux/dsc03149.jpg
>>
>>
>
>Hmm, thats odd. It seems to be coming from:
>reiserfs_commit_page -> reiserfs_add_ordered_list -> __add_jh(inline)
>
>I guess XFS may have left a buffer_head in an unusual state (with some
>private flag/b_private set), somehow, and perhaps that buffer_head has
>later been allocated for a page in a reiserfs write. Does this patch,
>below, help at all?
>
>I see one BUG check in __add_jh for non-NULL b_private, but can't see
>the top of your console output from the photos - is there a preceding
>line with "kernel BUG at ..." in it?
>
>cheers.
>
>
>
next prev parent reply other threads:[~2006-01-16 9:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 23:55 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Mattia Dongili
2006-01-11 1:00 ` Andrew Morton
2006-01-11 10:00 ` Pavel Machek
2006-01-11 11:24 ` Mattia Dongili
2006-01-11 18:40 ` Mattia Dongili
2006-01-12 22:08 ` first bisection results in -mm3 [was: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)] Mattia Dongili
2006-01-12 23:26 ` john stultz
2006-01-14 12:08 ` Mattia Dongili
2006-01-16 20:16 ` john stultz
2006-01-16 20:40 ` Mattia Dongili
2006-01-16 21:42 ` john stultz
2006-01-16 22:19 ` Andi Kleen
2006-01-16 22:41 ` john stultz
2006-01-17 16:43 ` Mattia Dongili
2006-01-17 16:45 ` Mattia Dongili
2006-01-17 0:49 ` john stultz
2006-01-17 17:49 ` Mattia Dongili
2006-01-17 19:11 ` john stultz
2006-01-17 22:49 ` Mattia Dongili
2006-01-18 10:47 ` Mattia Dongili
2006-01-24 22:27 ` john stultz
2006-01-24 23:04 ` Mattia Dongili
2006-01-24 23:48 ` john stultz
2006-01-25 0:12 ` john stultz
2006-01-25 18:12 ` Mattia Dongili
2006-01-11 10:02 ` 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Pavel Machek
2006-01-11 14:27 ` Mattia Dongili
2006-01-15 22:14 ` 2.6.15-mm3 bisection: git-xfs.patch makes reiserfs oops Mattia Dongili
2006-01-15 22:48 ` Nathan Scott
2006-01-15 23:22 ` Mattia Dongili
2006-01-16 9:29 ` Hans Reiser [this message]
2006-01-16 11:48 ` Christoph Hellwig
2006-01-16 15:50 ` Mattia Dongili
2006-01-17 3:27 ` Hans Reiser
2006-01-16 11:51 ` Mattia Dongili
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=43CB6796.4040104@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=malattia@linux.it \
--cc=nathans@sgi.com \
--cc=reiserfs-dev@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).