linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Jan Kara <jack@suse.cz>
Cc: reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix reiserfs oops on small fs
Date: Thu, 18 Nov 2004 09:09:43 -0500	[thread overview]
Message-ID: <1100786983.18452.35.camel@watt.suse.com> (raw)
In-Reply-To: <20041118114928.GD2767@atrey.karlin.mff.cuni.cz>

On Thu, 2004-11-18 at 12:49 +0100, Jan Kara wrote:
>   Hello!
> 
>   Attached patch fixes oops of reiserfs on a filesystem with just one
> bitmap block - current code always tries to return second bitmap even if
> there's not any. Could someone review it please so that it can be merged
> in mainline?

Hi Jan,

A slightly different form of this patch is in already.  Look for the
checks in bmap_hash_id.  Are you still able to reproduce this bug on
kernels newer than October 18?

-chris

  reply	other threads:[~2004-11-18 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 11:49 [PATCH] Fix reiserfs oops on small fs Jan Kara
2004-11-18 14:09 ` Chris Mason [this message]
2004-11-19  9:31   ` Jan Kara

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=1100786983.18452.35.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=jack@suse.cz \
    --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).