From: Pavel Emelyanov <xemul@parallels•com>
To: David Miller <davem@davemloft•net>,
Eric Dumazet <eric.dumazet@gmail•com>
Cc: Linux Netdev List <netdev@vger•kernel.org>
Subject: [PATCH 0/3] tcp: Validate recv queue on repair and related stuff
Date: Thu, 10 May 2012 15:49:13 +0400 [thread overview]
Message-ID: <4FABAB39.6090201@parallels.com> (raw)
As noted by Eric, no checks are performed when repairing data in tcp
read queue. He also suggested that the tcp_try_rmem_schedule() gets
out-lined for this.
This set does both of the above, more details are in patch comments.
Applies to net-next.
Thanks,
Pavel
next reply other threads:[~2012-05-10 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 11:49 Pavel Emelyanov [this message]
2012-05-10 11:49 ` [PATCH 1/3] tcp: Move rcvq sending to tcp_input.c Pavel Emelyanov
2012-05-10 12:00 ` Eric Dumazet
2012-05-11 3:25 ` David Miller
2012-05-10 11:50 ` [PATCH 2/3] tcp: Schedule rmem for rcvq repair send Pavel Emelyanov
2012-05-10 12:00 ` Eric Dumazet
2012-05-11 3:25 ` David Miller
2012-05-10 11:50 ` [PATCH 3/3] tcp: Out-line tcp_try_rmem_schedule Pavel Emelyanov
2012-05-10 12:00 ` Eric Dumazet
2012-05-11 3:25 ` David Miller
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=4FABAB39.6090201@parallels.com \
--to=xemul@parallels$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/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