From: David Miller <davem@davemloft.net>
To: buytenh@wantstofly.org
Cc: jarkao2@gmail.com, netdev@vger.kernel.org
Subject: Re: oopses since "net: Optimize memory usage when splicing from sockets"
Date: Thu, 30 Apr 2009 05:40:40 -0700 (PDT) [thread overview]
Message-ID: <20090430.054040.31760584.davem@davemloft.net> (raw)
In-Reply-To: <20090430124036.GN14729@mail.wantstofly.org>
From: Lennert Buytenhek <buytenh@wantstofly.org>
Date: Thu, 30 Apr 2009 14:40:36 +0200
> With your patch, at least the oops is gone, and I guess it makes
> sense and looks correct, so:
>
> Tested-by: Lennert Buytenhek <buytenh@wantstofly.org>
Thanks for testing Lennert.
I'll queue this up for -stable too.
next prev parent reply other threads:[~2009-04-30 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 3:16 oopses since "net: Optimize memory usage when splicing from sockets" Lennert Buytenhek
2009-04-30 8:43 ` Jarek Poplawski
2009-04-30 12:40 ` Lennert Buytenhek
2009-04-30 12:40 ` David Miller [this message]
2009-04-30 12:45 ` Lennert Buytenhek
2009-04-30 12:43 ` David Miller
2009-04-30 12:47 ` Jarek Poplawski
2009-04-30 12:30 ` [PATCH net-2.6] " Jarek Poplawski
2009-04-30 12:33 ` 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=20090430.054040.31760584.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=buytenh@wantstofly.org \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.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).