archive mirror
 help / color / mirror / Atom feed
From: Max Krasnyansky <>
Subject: [BK ChangeSet@1.1118.1.1] new module infrastructure for net_proto_family
Date: Wed, 23 Apr 2003 12:13:37 -0700	[thread overview]
Message-ID: <> (raw)

Hi Folks,

Can somebody (DaveM perhaps) please explain to me what the hell the following 
changset is doing in 2.5.68|ChangeSet@-7d

I've spent quite a bit of time looking into what's needed to fix socket module refcounting
issues and convicting DaveM and Alex that we need to fix them.
Here is the original thread

My patch was rejected without giving any technical explanation. I was waiting for Rusty's
__module_get() patch to get in, to release a new patch which addresses some issues that
came up during discussion.
Next thing you know, incomplete patch (changeset mentioned above) shows up in the BK and
2.5.68. Without even a simple note on the lkm. And completely ignoring discussion that 
we had about this very issue just a few weeks ago.

I don't mind of course if some other (better) patch is accepted instead of mine. But patch 
that went in is incomplete and buggy. It doesn't handle accept case properly and doesn't 
address the issue of the 'struct sock' ownership (read original thread for more details).



             reply	other threads:[~2003-04-23 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:13 Max Krasnyansky [this message]
2003-04-23 19:26 ` [BK ChangeSet@1.1118.1.1] new module infrastructure for net_proto_family Arnaldo Carvalho de Melo
2003-04-23 22:51   ` Max Krasnyansky
2003-04-23 23:30     ` David S. Miller
2003-04-24  1:41       ` Max Krasnyansky
2003-04-24  3:29         ` David S. Miller
2003-04-24 16:43           ` Max Krasnyansky
2003-04-24  6:44     ` Arnaldo Carvalho de Melo
2003-04-24 19:33       ` Max Krasnyansky
2003-04-24 23:02         ` Arnaldo Carvalho de Melo
2003-04-25  0:40           ` Max Krasnyansky

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).