All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: John Dalbec <jpdalbec@ysu.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: Trying to port data-logging to RH 2.4.18-19.7.x kernel
Date: 05 Feb 2003 11:00:38 -0500	[thread overview]
Message-ID: <1044460837.15684.876.camel@tiny.suse.com> (raw)
In-Reply-To: <3E411EA2.8000306@ysu.edu>

On Wed, 2003-02-05 at 09:24, John Dalbec wrote:

> > 
> > If not, you should be able to reproduce the oops on an unmodified redhat
> > kernel (compiled with SMP on), and I'd appreciate it if you could send
> > them a bug report as well.
> 
> I cannot reproduce the oops on an unmodified Red Hat kernel because they 
> don't call reiserfs_check_lock_depth in search_by_key.  That was added 
> by your data-logging patch.
> 

Heh, I added a bunch of those during the 2.4.0-test porting, I guess I
hit an odd bug during data logging coding and thought I needed a few
more.

Even though the check is only introduced in the data logging code, the
non-data logging code needs the BKL in search_by_key all the time.  So,
if you could please forward the details to redhat I'd appreciate it.

-chris



      reply	other threads:[~2003-02-05 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 14:41 Trying to port data-logging to RH 2.4.18-19.7.x kernel John Dalbec
2003-01-31 14:55 ` Chris Mason
2003-01-31 15:43   ` John Dalbec
2003-01-31 16:06     ` Chris Mason
2003-01-31 21:28       ` John Dalbec
2003-02-03 16:41         ` Chris Mason
2003-02-04 18:01           ` John Dalbec
2003-02-05 14:24           ` John Dalbec
2003-02-05 16:00             ` Chris Mason [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=1044460837.15684.876.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=jpdalbec@ysu.edu \
    --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 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.