public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 07 Dec 2001 23:06:48 +0100	[thread overview]
Message-ID: <3C113D78.F324F1B9@delusion.de> (raw)
In-Reply-To: <3C10D83E.81261D74@delusion.de> <3C10FDCF.D8E473A0@zip.com.au> <3C11394D.90101@us.ibm.com>

"David C. Hansen" wrote:

> I'm responsible for the release locking changes.  But, I don't think
> that the problems are a result of those changes.  There have been some
> other patches that might have caused the problem.  Take a look at this
> thread:

> Jens Axboe posted a patch.  I asked him:
> [...]

The patch that Jens posted was the fix for the oops I posted. The oops
was related to the bio stuff and not to the release() locking. I only
mentioned the keyboard stuff because I initially didn't know if there
was any connection between that and the oops.

> Udo, did you apply the patch that Jens sent?

Yes - and it cured the oops (the one in the thread you refer to), however
the keyboard problems are still there.

I guess there's something wrong with the changes you made, and it only
shows with the modifications that Andrew made - and since he says he
only fixed some bits of the code, the broken bits must have been there
before.

Regards,
Udo.

  reply	other threads:[~2001-12-07 22:07 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 [this message]
2001-12-07 22:16       ` Andrew Morton
2001-12-07 22:51         ` David C. Hansen
2001-12-07 23:17           ` Udo A. Steinberg
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=3C113D78.F324F1B9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox