Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: christophe varoqui <christophe.varoqui@free.fr>
To: Mike Anderson <andmike@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [BUG] scsi / genhd badness
Date: Mon, 28 Oct 2002 20:19:38 +0200	[thread overview]
Message-ID: <200210281919.38509.christophe.varoqui@free.fr> (raw)
In-Reply-To: <20021028180541.GB1234@beaverton.ibm.com>

> > 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
>
> This problem is do to a put_device still left in sg.c. The patch below
> is against ac5 to replace put_device with device_unregister which should
> remove this Badness.
>
Thank for your prompt response
Will try tomorow.

>
> The 2.5.44 SCSI subsystem still has some gaps in driverfs support. We
> currently do not have a hotplug function defined for scsi_bus. The call
> is still suppose to happen even if a bus does not define one, but I do
> not believe I have seen this happen.
>
yes, I tried to follow the million fonctions called after disk addition and 
got lost :) I just can't understand why the disks get added to driverfs on 
modprobe my_scsi_driver and not on "add-single-device".

regards,
cvaroqui

  reply	other threads:[~2002-10-28 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 15:20 [BUG] scsi / genhd badness christophe.varoqui
2002-10-28 18:05 ` Mike Anderson
2002-10-28 18:19   ` christophe varoqui [this message]
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=200210281919.38509.christophe.varoqui@free.fr \
    --to=christophe.varoqui@free.fr \
    --cc=andmike@us.ibm.com \
    --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