From: "Udo A. Steinberg" <reality@delusion.de>
To: "David C. Hansen" <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@zip.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: release() locking
Date: Sat, 08 Dec 2001 00:17:40 +0100 [thread overview]
Message-ID: <3C114E14.F6DC7937@delusion.de> (raw)
In-Reply-To: <3C10D83E.81261D74@delusion.de> <3C10FDCF.D8E473A0@zip.com.au> <3C11394D.90101@us.ibm.com> <3C113D78.F324F1B9@delusion.de> <3C113FB1.2000AFF1@zip.com.au> <3C1147F2.4070103@us.ibm.com>
"David C. Hansen" wrote:
>
> Andrew Morton wrote:
> >Maybe so. Can you identify the exact kernel version at which
> >the problem started?
Yes. I tried the entire 2.5.1-pre series:
-pre1 and -pre2 are fine.
-pre3 doesn't compile out of the box and with 3 trivial compile fixes to
pc_keyb.c shows the problem.
So anything including and after -pre3 is broken wrt. locking.
> The release() functions patch went into pre3. It looks like Jens' bio
> changes went into pre4.
Like I said before - it has nothing to do with Jens' bio stuff. Also the
fixes done by Andrew have nothing to do with it.
Moreover, if I back out the changes to pc_keyb.c, the problem goes away.
Regards,
Udo.
next prev parent reply other threads:[~2001-12-07 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 14:54 release() locking Udo A. Steinberg
2001-12-07 17:35 ` Andrew Morton
2001-12-07 17:42 ` Udo A. Steinberg
2001-12-07 21:49 ` David C. Hansen
2001-12-07 22:06 ` Udo A. Steinberg
2001-12-07 22:16 ` Andrew Morton
2001-12-07 22:51 ` David C. Hansen
2001-12-07 23:17 ` Udo A. Steinberg [this message]
2001-12-07 23:32 ` Andrew Morton
2001-12-07 23:54 ` Udo A. Steinberg
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=3C114E14.F6DC7937@delusion.de \
--to=reality@delusion.de \
--cc=akpm@zip.com.au \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.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 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.