netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kovacs Krisztian <hidden@balabit.hu>
To: kuznet@ms2.inr.ac.ru
Cc: "David S. Miller" <davem@redhat.com>,
	jmorris@redhat.com, netdev@oss.sgi.com,
	linux-net@vger.kernel.org, Balazs Scheidler <bazsi@balabit.hu>
Subject: Re: [PATCH] ipv4 tcp autobind problem
Date: Tue, 07 Oct 2003 14:35:50 +0200	[thread overview]
Message-ID: <3F82B326.9050508@balabit.hu> (raw)
In-Reply-To: <200310071156.PAA31530@yakov.inr.ac.ru>


   Hi,

kuznet@ms2.inr.ac.ru wrote:
> Right place to finish tracking is when socket is removed from TCP
> hash tables, and to start tracking is when the socket is inserted
> to TCP hash tables. BTW you would not see the problem with binding
> if it was made right.

   Thanks for the reply. In the meantime, although because of slightly 
different reasons, we also came to the same conclusion. Right now I'm 
testing a version in which our "unassign" hook is removed from 
inet_release(), and added to udp_v4_unhash() and tcp_put_port().
However, I'm not quite sure there won't be locking problems when calling 
our hook from these places.

-- 
   Regards,
     Krisztian KOVACS

  reply	other threads:[~2003-10-07 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030930024320.5aca8ddc.davem@redhat.com>
2003-09-30 12:37 ` Fw: Re: [PATCH] ipv4 tcp autobind problem kuznet
2003-09-30 12:37   ` David S. Miller
2003-09-30 14:19   ` Kovacs Krisztian
2003-10-07 11:56     ` kuznet
2003-10-07 12:35       ` Kovacs Krisztian [this message]
2003-09-29 13:05 Kovacs Krisztian
2003-09-30  5:22 ` David S. Miller
2003-09-30  7:14   ` Kovacs Krisztian

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=3F82B326.9050508@balabit.hu \
    --to=hidden@balabit.hu \
    --cc=bazsi@balabit.hu \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).