public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, mochel@osdl.org
Subject: Re: [PATCH] scsi_host sysfs updates scsi-misc-2.5 [0/2]
Date: Mon, 12 May 2003 13:35:07 -0700	[thread overview]
Message-ID: <20030512203507.GC3226@beaverton.ibm.com> (raw)
In-Reply-To: <1052770234.1769.75.camel@mulgrave>

James Bottomley [James.Bottomley@steeleye.com] wrote:
> On Mon, 2003-05-12 at 13:41, Mike Anderson wrote:
> > I would like to have feedback from Mochel on the device_initialize
> > call.
> > 
> > The documentation I have read indicates the device_initialize call was to
> > allow the struct device to be usable for reference counting. I think we
> > should determine if that is the intent and can we call kobj_set_kset_s
> > in device_initialize.
> > 
> > Another option may be to set the ktype value on our struct device
> > kobject until device_add overrides this with the call to kobj_set_kset_s.
> 
> I can confirm that moving kobj_set_kset_s fixes my boot up problem (with
> your other patch).  However, now I'm running into an obscure slab
> corruption issue, so I suspect the move has to be more carefully
> orchestrated.

I checked out that setting kobj.ktype also seems to solve the problem
(using a hacked version of scsi_debug and calling scsi_register followed
by a call to scsi_unregister). This would give a more localized work
around, but device_initialize kobj_set_kset_s may be a better choice.

What slab size? (size-512)

-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2003-05-12 20:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  6:33 [PATCH] scsi_host sysfs updates scsi-misc-2.5 [0/2] Mike Anderson
2003-05-09  6:34 ` [PATCH] scsi_host sysfs updates scsi-misc-2.5 [1/2] Mike Anderson
2003-05-09  6:35   ` [PATCH] scsi_host sysfs updates scsi-misc-2.5 [2/2] Mike Anderson
2003-05-09  6:59     ` Christoph Hellwig
2003-05-09  7:50       ` Mike Anderson
2003-05-09  8:21         ` Mike Anderson
2003-05-12  3:57 ` [PATCH] scsi_host sysfs updates scsi-misc-2.5 [0/2] James Bottomley
2003-05-12  6:38   ` Mike Anderson
2003-05-12 17:50     ` James Bottomley
2003-05-12 17:59       ` James Bottomley
2003-05-12 18:41         ` Mike Anderson
2003-05-12 20:10           ` James Bottomley
2003-05-12 20:35             ` Mike Anderson [this message]
2003-05-12 20:42               ` James Bottomley
2003-05-12 20:53                 ` James Bottomley
2003-05-12 21:49                 ` Mike Anderson
2003-05-12 21:50                   ` James Bottomley
2003-05-12 22:15                     ` Mike Anderson
2003-05-14  0:00           ` Patrick Mochel
2003-05-12 18:18       ` Mike Anderson
2003-05-12 15:15 ` Andrew Vasquez
2003-05-13 18:51   ` Mike Anderson

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=20030512203507.GC3226@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mochel@osdl.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