From: David Miller <davem@davemloft.net>
To: jwerner@chromium.org
Cc: davej@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, kaber@trash.net, yoshfuji@linux-ipv6.org,
jmorris@namei.org, kuznet@ms2.inr.ac.ru, eric.dumazet@gmail.com,
snanda@chromium.org, msb@chromium.org
Subject: Re: [PATCH] tcp: Avoid infinite loop on recvmsg bug
Date: Mon, 10 Dec 2012 15:23:56 -0500 (EST) [thread overview]
Message-ID: <20121210.152356.1449949752496567529.davem@davemloft.net> (raw)
In-Reply-To: <CAODwPW_P_UNGV8rRC7hFC+PBrWeu64ODu5mTby=9GCqMnyDtdQ@mail.gmail.com>
I've tossed these two patches under the carpet, so you'll need to
repost whichever one you want me to consider.
Basically, discussing old patches is pretty useless without a resend
to get it back into the fore-front of the patchwork queue. So please
don't reference old stale patches without an associated repost like
this.
Thanks.
next prev parent reply other threads:[~2012-12-10 20:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 0:15 [PATCH] tcp: Replace infinite loop on recvmsg bug with proper crash Julius Werner
2012-11-07 1:39 ` Dave Jones
2012-11-07 1:51 ` Julius Werner
2012-11-07 15:54 ` Dave Jones
2012-11-07 16:29 ` [PATCH] tcp: Replace infinite loop on recvmsg bug with proper crashusers Eric Dumazet
2012-11-07 16:43 ` Dave Jones
2012-11-07 17:05 ` Eric Dumazet
2012-11-07 17:15 ` Dave Jones
2012-11-07 19:32 ` Julius Werner
2012-11-07 19:33 ` [PATCH] tcp: Avoid infinite loop on recvmsg bug Julius Werner
2012-11-07 19:40 ` Eric Dumazet
2012-11-07 21:14 ` Julius Werner
2012-11-07 23:33 ` Eric Dumazet
2012-11-07 23:42 ` Eric Dumazet
2012-11-08 2:25 ` Julius Werner
2012-11-09 3:29 ` Eric Dumazet
2012-12-10 19:33 ` Julius Werner
2012-12-10 20:23 ` David Miller [this message]
2012-11-07 1:51 ` [PATCH] tcp: Replace infinite loop on recvmsg bug with proper crash Eric Dumazet
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=20121210.152356.1449949752496567529.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=jwerner@chromium.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=snanda@chromium.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).