public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: eo@nebensachen.de, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Block: Trouble with kobject initialisation for blk_cmd_filter
Date: Tue, 9 Sep 2008 15:18:52 +0200	[thread overview]
Message-ID: <20080909131850.GL20055@kernel.dk> (raw)
In-Reply-To: <20080909214602L.fujita.tomonori@lab.ntt.co.jp>

On Tue, Sep 09 2008, FUJITA Tomonori wrote:
> On Tue, 9 Sep 2008 12:28:45 +0200
> Jens Axboe <jens.axboe@oracle.com> wrote:
> 
> > On Fri, Sep 05 2008, Elias Oltmanns wrote:
> > > Hi all,
> > > 
> > > current usage of the kobject in struct blk_cmd_filter is flawed. Doing
> > > # modprobe -r sd-mod && modprobe sd-mod
> > > while, for instance, a usb-stick is plugged in currently results in
> > > nasty warnings and a dump_stack(). Since blk_cmd_filter is embedded in
> > > struct request_queue, I don't see the need for a kobject anyway. What
> > > about the much simpler option of a struct attribute_group in this
> > > particular case?
> > > 
> > > This would imply that the cmd_filter subdirectory would appear under
> > > sda/queue/ rather than sda/ (which is probably the right place) but,
> > > alas, we have to keep compatibility in mind. So I've made some changes
> > > to sysfs along the way in order to provide a legacy symlink. I'd have to
> > > seperate these two changes for submission but I wanted to know your
> > > opinion about it all first.
> > > 
> > > Thinking about it now makes me wonder whether this is too much for a rc
> > > patch and whether we should just allocate the struct blk_cmd_filter
> > > dynamically and have done with it. Anyway, tell me what you think.
> > 
> > I think this patch is a step in the right direction, lets get rid of
> > that pesky kobject just for the cmdfilter. Can you resend the patch
> > _without_ the sysfs changes and link support? We haven't released a
> > kernel with cmd filter support yet, so we can change the location still
> > and not have to worry about compatability.
> 
> The sysfs changes looks too much for 2.6.27-rcX but without the sysfs
> changes, we have the cmdfilter under /sys/block/sda/queue/, right? We
> don't need to worry about compatibility, but /sys/block/sda is more
> appropriate? (though I don't think that the cmd filter is a good idea
> so I don't care much).

I agree, under sda/ makes a lot more sense than under sda/queue/

> Jens, would it be better to just disable the cmdfilter stuff for
> 2.6.27? It's too late for another try to fix this broken stuff, I
> guess.

Yeah, it's certainly starting to look like it... The amount of changes
to unbreak it are too large to submit now, so lets postpone it until
2.6.28.

-- 
Jens Axboe


  reply	other threads:[~2008-09-09 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 16:48 Block: Trouble with kobject initialisation for blk_cmd_filter Elias Oltmanns
2008-09-09 10:28 ` Jens Axboe
2008-09-09 12:45   ` FUJITA Tomonori
2008-09-09 13:18     ` Jens Axboe [this message]
2008-09-09 16:57       ` Elias Oltmanns
2008-09-10  2:43         ` FUJITA Tomonori
2008-09-15 19:55       ` Elias Oltmanns
2008-09-15 20:17         ` FUJITA Tomonori
2008-09-15 20:49           ` Elias Oltmanns
2008-09-15 21:31             ` FUJITA Tomonori

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=20080909131850.GL20055@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=eo@nebensachen.de \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=greg@kroah.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