From: Paul Clements <Paul.Clements@SteelEye.com>
To: Jens Axboe <axboe@suse.de>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: nbd oops on unload.
Date: Wed, 18 Feb 2004 12:39:11 -0500 [thread overview]
Message-ID: <4033A33F.FF279C05@SteelEye.com> (raw)
In-Reply-To: 20040218071752.GB27190@suse.de
Jens Axboe wrote:
>
> On Wed, Feb 18 2004, Paul Clements wrote:
> > Dave Jones wrote:
> > >
> > > modprobe nbd ; rmmod nbd was enough to reproduce this one..
> > > (2.6.3rc4)
> >
> > hmmm...I'll look into it...out of curiosity, are you using any "unusual"
> > kernel config options? I've done the same test myself many times and
> > have not seen any problems...
>
> It looks like 'the usual' 'several devices sharing a queue' oops on
> unload.
Ahh, cleanup was being done in the wrong order.
Patch coming shortly...
--
Paul
next prev parent reply other threads:[~2004-02-18 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:47 nbd oops on unload Dave Jones
2004-02-18 6:00 ` Paul Clements
2004-02-18 7:17 ` Jens Axboe
2004-02-18 17:39 ` Paul Clements [this message]
2004-02-18 22:03 ` nbd oops on unload. [PATCH x2] Paul Clements
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=4033A33F.FF279C05@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=axboe@suse.de \
--cc=davej@redhat.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