From: Glauber Costa <glommer@parallels•com>
To: Pavel Emelyanov <xemul@parallels•com>
Cc: Linux Netdev List <netdev@vger•kernel.org>,
David Miller <davem@davemloft•net>, Tejun Heo <tj@kernel•org>,
Eric Dumazet <eric.dumazet@gmail•com>
Subject: Re: [PATCH 2/3] tcp: Initial repair mode
Date: Tue, 6 Mar 2012 17:11:47 +0400 [thread overview]
Message-ID: <4F560D13.4000404@parallels.com> (raw)
In-Reply-To: <4F55DF12.6030001@parallels.com>
On 03/06/2012 01:55 PM, Pavel Emelyanov wrote:
> This includes (according the the previous description):
>
> * TCP_REPAIR sockoption
>
> This one just puts the socket in/out of the repair mode.
> Allowed for CAP_SYS_ADMIN and for closed/establised sockets only.
> When repair mode is turned off and the socket happens to be in
> the established state the window probe is sent to the peer to
> 'unlock' the connection.
Why not CAP_NET_ADMIN, or something similar?
next prev parent reply other threads:[~2012-03-06 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 9:54 [RFC][PATCH 0/3] TCP connection repair (v2) Pavel Emelyanov
2012-03-06 9:55 ` [PATCH 1/3] tcp: Move code around Pavel Emelyanov
2012-03-06 9:55 ` [PATCH 2/3] tcp: Initial repair mode Pavel Emelyanov
2012-03-06 13:11 ` Glauber Costa [this message]
2012-03-06 20:16 ` David Miller
2012-03-06 9:55 ` [PATCH 3/3] tcp: Repair socket queues Pavel Emelyanov
2012-03-06 21:14 ` [RFC][PATCH 0/3] TCP connection repair (v2) David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-03-28 15:36 [PATCH net-next 0/3] TCP connection repair (v3) Pavel Emelyanov
2012-03-28 15:37 ` [PATCH 2/3] tcp: Initial repair mode Pavel Emelyanov
2012-03-28 17:20 ` Glauber Costa
2012-03-29 9:52 ` Pavel Emelyanov
2012-03-28 20:39 ` Ben Hutchings
2012-03-29 9:53 ` Pavel Emelyanov
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=4F560D13.4000404@parallels.com \
--to=glommer@parallels$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
--cc=xemul@parallels$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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