From: "Feldman, Scott" <scott.feldman@intel.com>
To: "'Arnd Bergmann'" <arnd@bergmann-dalldorf.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: [patch] e100 schedule while atomic
Date: Mon, 30 Sep 2002 14:48:03 -0700 [thread overview]
Message-ID: <288F9BF66CD9D5118DF400508B68C44604758A6C@orsmsx113.jf.intel.com> (raw)
Arnd wrote:
> Running e100 on linux-2.5.39 showed that the driver
> incorrectly holds a lock while calling request_irq(), which
> does kmalloc().
>
> This patch appears to solve the problem. Not sure if it is
> correct, but something like it has to be done.
Thanks for pointing this out. I don't think the lock needs to be held at
all in e100_open, so we'll look into cleaning that up. Regardless, we'll
included a fix for this problem in our next set of patches to Jeff.
-scott
next reply other threads:[~2002-09-30 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 21:48 Feldman, Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-28 20:53 [patch] e100 schedule while atomic Arnd Bergmann
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=288F9BF66CD9D5118DF400508B68C44604758A6C@orsmsx113.jf.intel.com \
--to=scott.feldman@intel.com \
--cc=arnd@bergmann-dalldorf.de \
--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;
as well as URLs for NNTP newsgroup(s).