From: "David C. Hansen" <haveblue@us.ibm.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Udo A. Steinberg" <reality@delusion.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: release() locking
Date: Fri, 07 Dec 2001 13:49:01 -0800 [thread overview]
Message-ID: <3C11394D.90101@us.ibm.com> (raw)
In-Reply-To: <3C10D83E.81261D74@delusion.de> <3C10FDCF.D8E473A0@zip.com.au>
Andrew Morton wrote:
>"Udo A. Steinberg" wrote:
>
>>Hi Andrew,
>>
>>According to Linus' 2.5.1-pre changelog, the release locking changes
>>introduced in -pre5 are your work. Those changes, however, seem to
>>break the keyboard driver:
>>
>>keyboard: Timeout - AT keyboard not present?(f4)
>>
>>Other people (i.e. Mike Galbraith) have been experiencing the same.
>>
>wasntmeididntdoit
>
>>Do you have an updated patch which fixes those issues? -pre6 still
>>contains the same stuff as -pre5 and if it's broken then Linus should
>>probably back it out.
>>
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:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100745930928683&w=2
Jens Axboe posted a patch. I asked him:
> So, what was the actual problem?
bio_alloc() not waiting on the reserved pool for free entries, even
though __GFP_WAIT was set. No need for __GFP_IO in that case too.
Udo, did you apply the patch that Jens sent?
next prev parent reply other threads:[~2001-12-07 21:49 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 [this message]
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
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=3C11394D.90101@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=reality@delusion.de \
/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.