From: Andreas Herrmann <aherrman@arcor.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Hansjoerg Lipp <hjlipp@web.de>,
gigaset307x-common@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kkeil@suse.de
Subject: Re: [PATCH] gigaset: fix module reference counting
Date: Mon, 23 Jun 2008 09:32:27 +0200 [thread overview]
Message-ID: <20080623073227.GA6033@obelix> (raw)
In-Reply-To: <4855A145.90803@imap.cc>
On Mon, Jun 16, 2008 at 01:09:57AM +0200, Tilman Schmidt wrote:
> On 2008-06-07 00:39, Andreas Herrmann wrote:
> > bas_gigaset can't be unloaded due to wrong module reference counting.
> > Ensure that module_put is called whenever a channel is freed.
>
> I'm not quite happy with that patch. Specifically, I see a risk of
> module_put being called too often.
> Could you explain in some more detail what bug you are trying to fix?
> Do you have a sequence of events which leads to a situation where the
> bas_gigaset module cannot be unloaded but should be?
I've tried to reproduce the problem doing various tests -- but without
success.
Then i've checked the code and there was already this fix:
commit e468c04894f36045cf93d1384183a461014b6840 (Gigaset: permit module unload)
This was commited after 2.6.24 was released.
And (shit happens!) on the machine where I've previously tested the
stuff I had also an 2.6.24 kernel installed.
So it seems that I have mixed up different kernel versions when I've
tested my patch. Because with current git-tree bas_gigaset can be
unloaded without any problems.
Sorry for the noise.
Regards,
Andreas
next prev parent reply other threads:[~2008-06-23 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 22:39 [PATCH] gigaset: fix module reference counting Andreas Herrmann
2008-06-15 23:09 ` Tilman Schmidt
2008-06-23 7:32 ` Andreas Herrmann [this message]
2008-06-23 7:38 ` Tilman Schmidt
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=20080623073227.GA6033@obelix \
--to=aherrman@arcor.de \
--cc=akpm@linux-foundation.org \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=hjlipp@web.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.