From: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>
To: Andrew Hendry <ahendry@tusc.com.au>
Cc: Herbert Poetzl <herbert@13thfloor.at>,
eis@baty.hanse.de, linux-x25@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: x25_create initializing socket data twice ...
Date: Thu, 3 Mar 2005 16:37:13 -0300 [thread overview]
Message-ID: <20050303193712.GC1587@cathedrallabs.org> (raw)
In-Reply-To: <1109820054.3014.146.camel@localhost.localdomain>
Hi,
> On the same path sk_set_owner also gets called twice, I think this
> causes double module use count when creating sockets. Module use count
> need some attention all over x25.
I'm working on it already. I hope to send patches soon.
Is linux-x25 list alive? if not, perhaps we should add netdev to Cc.
--
Aristeu
prev parent reply other threads:[~2005-03-03 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 1:14 x25_create initializing socket data twice Herbert Poetzl
2005-03-03 3:20 ` Andrew Hendry
2005-03-03 19:37 ` Aristeu Sergio Rozanski Filho [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=20050303193712.GC1587@cathedrallabs.org \
--to=aris@cathedrallabs.org \
--cc=ahendry@tusc.com.au \
--cc=eis@baty.hanse.de \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@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