From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH (resend)]: SCSI: fix /proc memory leak in the SCSI core
Date: Sun, 22 Feb 2009 13:46:03 -0600 [thread overview]
Message-ID: <1235331963.4531.61.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0902221431170.30449-100000@netrider.rowland.org>
On Sun, 2009-02-22 at 14:34 -0500, Alan Stern wrote:
> On Sun, 22 Feb 2009, James Bottomley wrote:
>
> > OK, but resending a patch you expressed reservations about putting in
> > without testing doesn't really help me. I need a way to get comfortable
> > with its safety.
> >
> > So, what about this alternative fix instead: if the removal were moved
> > to scsi_host_put(), that would address all the problems and have the
> > advantage that everyone will test it ...
>
> I thought of doing it that way too. It has the disadvantage of
> exposing part of the proc interface to userspace before the host is
> registered. Now, since all we're adding is the host's directory, maybe
> this doesn't matter. But it didn't seem like a good idea.
It's current behaviour (and has been so for all of git history) with no
reported bugs.
All it's doing is creating a proc dir ... it's not exposing any
interfaces within, so from a theoretical standpoint it's perfectly OK.
The necessity for finding a legacy system to test was precisely because
you moved it.
James
next prev parent reply other threads:[~2009-02-22 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 15:52 [PATCH (resend)]: SCSI: fix /proc memory leak in the SCSI core Alan Stern
2009-02-22 17:40 ` James Bottomley
2009-02-22 19:34 ` Alan Stern
2009-02-22 19:46 ` James Bottomley [this message]
2009-02-23 0:56 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 15:09 Tony Battersby
2009-02-27 21:50 ` Alan Stern
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=1235331963.4531.61.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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