From: Greg KH <greg@kroah.com>
To: "Rachmel, Nir (Nir)" <rachmel@avaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops on hot insertion of USB
Date: Fri, 11 Apr 2008 21:29:18 -0700 [thread overview]
Message-ID: <20080412042918.GA13154@kroah.com> (raw)
In-Reply-To: <11486DD9B957EA488E21C44BC8737EFC987F23@307622ANEX5.global.avaya.com>
On Thu, Apr 10, 2008 at 03:06:05PM +0200, Rachmel, Nir (Nir) wrote:
> Hi,
>
> I am running linux kernel version 2.6.14.7, and have a problem
> when
> inserting / removing a disk-on-key device from my system: I get
> a
> "kernel oops". Using some debugging tools I managed to trace the
> problem down to an event of "double free" that occurs within the
> hot
> insertion module.
>
> googling didn't help much. Is this a known issue which is
> resolved in
> later kernel versions?
Yes it is, please upgrade :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-04-12 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 13:06 Kernel Oops on hot insertion of USB Rachmel, Nir (Nir)
2008-04-10 13:48 ` Bart Van Assche
2008-04-12 4:29 ` Greg KH [this message]
[not found] ` <11486DD9B957EA488E21C44BC8737EFC55F379@307622ANEX5.global.avaya.com>
2008-04-12 16:59 ` Greg KH
2008-04-12 19:08 ` Yinghai Lu
2008-04-12 19:47 ` Simon Holm Thøgersen
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=20080412042918.GA13154@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rachmel@avaya.com \
/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