Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: christophe.varoqui@free.fr
To: linux-scsi@vger.kernel.org
Subject: [BUG] scsi / genhd badness
Date: Mon, 28 Oct 2002 16:20:30 +0100 (MET)	[thread overview]
Message-ID: <1035818430.3dbd55be25447@imp.free.fr> (raw)

Hello, 
 
I'd like to report an annoying behaviour : 
 
On a server with scsi disk behind an aic7xxx, kernel 2.5.44-ac4, each time I 
remove a disk from the linux scsi subsystem (echo "scsi remove-single-device a 
b c d">/proc/scsi/scsi) I get the following oops (server survive) : 
 
Badness in put_device at drivers/base/core.c:139 
Call Trace: 
 [<c01d12ae>] put_device+0xde/0xf0 
 [<c022c1ff>] sg_detach+0x8f/0x1f0 
 [<c02121d8>] proc_scsi_gen_write+0x338/0x4b0 
 [<c014d6c6>] open_namei+0xa6/0x400 
 [<c01658e0>] proc_file_write+0x40/0x50 
 [<c014047c>] vfs_write+0xdc/0x150 
 [<c014058e>] sys_write+0x3e/0x60 
 [<c010772b>] syscall_call+0x7/0xb 
 
the block event gets passed to the hotplug layer. 
Driverfs loose the $driverfs/bus/block/device/ (and $driverfs/root/) disk entry 
: right 
 
On the other hand, when I re-add this disk, hotplug is not notified and disk 
entry does not re-appear in driverfs. 
 
Other sybsystems are not similarily affected : device-mapper gives the oops on 
device map removal but devmap addition get rightly notified to userspace. 
 
Is it a known short-coming ? 
 
regards, 
cvaroqui 

             reply	other threads:[~2002-10-28 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 15:20 christophe.varoqui [this message]
2002-10-28 18:05 ` [BUG] scsi / genhd badness Mike Anderson
2002-10-28 18:19   ` christophe varoqui
2002-10-29  8:23   ` christophe.varoqui

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=1035818430.3dbd55be25447@imp.free.fr \
    --to=christophe.varoqui@free.fr \
    --cc=linux-scsi@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