From: "Stephen C. Tweedie" <sct@redhat.com>
To: R.Oehler@GDImbH.com
Cc: linux-mm@kvack.org
Subject: Re: recursive lock-enter-deadlock
Date: Wed, 21 Nov 2001 10:56:31 +0000 [thread overview]
Message-ID: <20011121105631.B2500@redhat.com> (raw)
In-Reply-To: <XFMail.20011121111913.R.Oehler@GDImbH.com>; from R.Oehler@GDImbH.com on Wed, Nov 21, 2001 at 11:19:13AM +0100
Hi,
On Wed, Nov 21, 2001 at 11:19:13AM +0100, R.Oehler@GDImbH.com wrote:
> A short question (I don't have a recent 2.4.x at hand, currently):
>
> Is this recursive lock-enter-deadlock (2.4.0) fixed in newer kernels?
Yes. Seriously, 2.4.0 is so old and so full of bugs like this that
it's really not worth spending any effort looking for problems like
that in it.
Cheers,
Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-11-21 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 10:19 R.Oehler
2001-11-21 10:56 ` Stephen C. Tweedie [this message]
2001-11-21 11:52 ` R.Oehler
2001-11-21 12:35 ` Stephen C. Tweedie
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=20011121105631.B2500@redhat.com \
--to=sct@redhat.com \
--cc=R.Oehler@GDImbH.com \
--cc=linux-mm@kvack.org \
/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