From: John Dalbec <jpdalbec@ysu.edu>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Trying to port data-logging to RH 2.4.18-19.7.x kernel
Date: Wed, 05 Feb 2003 09:24:34 -0500 [thread overview]
Message-ID: <3E411EA2.8000306@ysu.edu> (raw)
In-Reply-To: 1044290509.15685.391.camel@tiny.suse.com
Chris Mason wrote:
> So your two basic choices are adding the BKL to reiserfs_read_inode2, or
> going into the nfsd source and putting them around the iget4 call. You
> might want to double check to see if their source had the BKL in
> reiserfs_read_inode2 before you started the data logging port.
It did not.
>
> 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.
>
> -chris
>
>
>
next prev parent reply other threads:[~2003-02-05 14:24 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 [this message]
2003-02-05 16:00 ` Chris Mason
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=3E411EA2.8000306@ysu.edu \
--to=jpdalbec@ysu.edu \
--cc=mason@suse.com \
--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.