netdev - Re: [PATCH v3] net-tcp: TCP/IP stack bypass for loopback connections

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: <20120919.171759.954995920168438601.davem@davemloft.net>
Date:	Wed, 19 Sep 2012 17:17:59 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	brutus@...gle.com, edumazet@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH v3] net-tcp: TCP/IP stack bypass for loopback
 connections

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 19 Sep 2012 23:03:54 +0200

> On Wed, 2012-09-19 at 16:34 -0400, David Miller wrote:
> 
>> I have an idea on how to handle this.
>> 
>> In drivers/net/loopback.c:loopback_tx(), skip the SKB orphan operation
>> if there is a friend socket at skb->friend.
>> 
>> When sending such friend SKBs out at connection startup, arrange it
>> such that the skb->destructor will zap the skb->friend pointer to
>> NULL.
>> 
>> Also, in skb_orphan*(), if necessary, set skb->friend to NULL.
>> 
>> skb->sk will hold a reference to the socket, and since skb->friend
>> will be equal, this will make sure a pointer to an unreferenced
>> socket does not escape.
> 
> I now am wondering if we still need skb->friend field.
> 
> If skb->sk is not zeroed by a premature skb_orphan(), then
> 
> skb->sk->sk_friend gives the friend ?

Good point.
--
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