From: Jeff Mahoney <jeffm@suse.com>
To: Damien Wyart <damien.wyart@free.fr>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1 + reiser* from -rc1-mm1 : BUG with reiserfs
Date: Thu, 19 Jan 2006 10:56:33 -0500 [thread overview]
Message-ID: <43CFB6B1.8000908@suse.com> (raw)
In-Reply-To: <20060119094205.GA14907@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Damien Wyart wrote:
> Hello,
>
>>>> Sigh. Ok. Back out the reiserfs patches
> * Jeff Mahoney <jeffm@suse.com> [2006-01-18 18:17]:
>> Just the on-demand bitmap stuff.
>
> New test this morning with latest 2.6.16-rc1-git pulled with git, and
> all reiserfs and reiser4 patches from -rc1-mm1, EXCEPT the three
> on-demand bitmap for reiserfs. And when booting, the systems half
> crashes with this error. So I guess the bad patches are not only the
> ones for on-demand bitmap...
Indeed. What's happening here is that the SB_AP_BITMAP(s) macro is
evaluating to NULL since other places use it too early.
As I said, these patches should never have been sent out.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDz7axLPWxlyuTD7IRArQxAJ9d6gijEPjXxKnXcC5FNWUuT95eqACcDURU
HOTcl/BhvTd2RwAO4fd/ZZ0=
=Ct4w
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-01-19 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 12:26 2.6.16-rc1 + reiser* from -rc1-mm1 : BUG with reiserfs Damien Wyart
2006-01-18 22:50 ` Jeff Mahoney
2006-01-18 23:04 ` Rafael J. Wysocki
2006-01-18 23:17 ` Jeff Mahoney
2006-01-19 9:42 ` Damien Wyart
2006-01-19 9:56 ` Damien Wyart
2006-01-19 15:56 ` Jeff Mahoney [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=43CFB6B1.8000908@suse.com \
--to=jeffm@suse.com \
--cc=akpm@osdl.org \
--cc=damien.wyart@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.