From: Christoph Hellwig <hch@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] s390 (2/7): common i/o layer.
Date: Mon, 6 Oct 2003 15:55:59 +0100 [thread overview]
Message-ID: <20031006155559.A21462@infradead.org> (raw)
In-Reply-To: <OF79F7FC5D.894CD912-ONC1256DB7.0051545B-C1256DB7.00516DD4@de.ibm.com>; from schwidefsky@de.ibm.com on Mon, Oct 06, 2003 at 04:49:25PM +0200
On Mon, Oct 06, 2003 at 04:49:25PM +0200, Martin Schwidefsky wrote:
> > > Just checked. You right about chp_release which should do
> > > a kfree on the struct channel_path object. But the two
> > > other release functions are really dummy functions because
> > > cu3088_root_dev and iucv_root are static structures.
> >
> > Even in that case you're screwed in case they are in modules..
>
> Why? The root device are registered in the module init function
> and unregistered in the module exit function. I fail to see the
> problem.
You can still have a reference to the object when the module is unloaded.
unregistered != last reference is gone
next prev parent reply other threads:[~2003-10-06 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 14:49 [PATCH] s390 (2/7): common i/o layer Martin Schwidefsky
2003-10-06 14:55 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 15:59 Martin Schwidefsky
2003-10-06 15:37 Martin Schwidefsky
2003-10-06 15:46 ` viro
2003-10-06 14:40 Martin Schwidefsky
2003-10-06 14:44 ` Christoph Hellwig
2003-10-06 9:24 Martin Schwidefsky
2003-10-06 14:01 ` Christoph Hellwig
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=20031006155559.A21462@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@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