netdev - Re: What's the status of TCP friends?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140317031605.GA22502@gmail.com>
Date:	Mon, 17 Mar 2014 11:16:05 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	netdev <netdev@...r.kernel.org>, Li Yu <bingtian.ly@...bao.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Bruce Brutus Curtis <brutus@...gle.com>,
	Weiping Pan <panweiping3@...il.com>
Subject: Re: What's the status of TCP friends?

On Sun, Mar 16, 2014 at 07:03:39AM -0700, Eric Dumazet wrote:
> On Sun, 2014-03-16 at 17:07 +0800, Zheng Liu wrote:
> > Hi all,
> > 
> > Until now the TCP friends patch set doesn't be applied.  Now what's the
> > status of TCP friends?  Is it applicable to be merged into upstream
> > kernel?  Any problem that needs to be fixed?  Please let me know if I
> > can help.
> 
> Well, last attempts showed that while the idea sounded cool,
> implementation opened many races and added quite a lot of complexity in
> fast path.

Thanks for letting me know the current status of this patch set.

> 
> We have AF_UNIX with a lot of problems in it, do we really want to bring
> these AF_UNIX problems to AF_INET ?

Please bear with me because I am a newbie.  Out of curiosity, what's the
problem in AF_UNIX?

> 
> I would rather spend time on AF_UNIX if it doesn't fit your needs right
> now, or consider jumping to KDBUS modern design.
> 
> Using AF_INET for IPC is poor choice.

The reason why we use AF_INET for IPC rather than use AF_UNIX is that we
have two applications that need to communicate with each other.  They
could be deployed on the same server or different servers.  So obviously
if we use AF_INET, we just need to indicate a IP address in config file.
That sounds rational and maintainable for our operation team.

Regards,
                                                - Zheng
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html