From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Add release function to sd for scsi_disk structure
Date: Wed, 22 Oct 2003 17:17:31 +0100 [thread overview]
Message-ID: <20031022171731.B24857@infradead.org> (raw)
In-Reply-To: <20031022160855.GC1684@beaverton.ibm.com>; from andmike@us.ibm.com on Wed, Oct 22, 2003 at 09:08:55AM -0700
On Wed, Oct 22, 2003 at 09:08:55AM -0700, Mike Anderson wrote:
> Christoph Hellwig [hch@infradead.org] wrote:
> >
> > This looks like a reasonable bandaid until the block layer is fixed.
> >
>
> Since I do not know the extent of the block layer changes maybe my
> assumption is incorrect, but wouldn't will still need a release of some
> kind to know when it is safe to do a free?
We'll have to see. My assumption would be that freeing any private
data should be fine after ->remove. If that's not going to be guaranteed
we should try to make your patch a bit more generic (e.g. no sd-specific
ktype)
prev parent reply other threads:[~2003-10-22 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 7:40 [PATCH] Add release function to sd for scsi_disk structure Mike Anderson
2003-10-21 8:26 ` Christoph Hellwig
2003-10-22 16:08 ` Mike Anderson
2003-10-22 16:17 ` Christoph Hellwig [this message]
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=20031022171731.B24857@infradead.org \
--to=hch@infradead.org \
--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