From: Gregory Haskins <gregory.haskins@gmail.com>
To: Patrick Mullaney <pmullaney@novell.com>
Cc: linux-kernel@vger.kernel.org, alacrityvm-devel@lists.sourceforge.net
Subject: Re: [Alacrityvm-devel] [PATCH] vbus-enet: fix l4ro pool non-atomic allocations in softirq context
Date: Tue, 27 Oct 2009 17:37:16 -0400 [thread overview]
Message-ID: <4AE7680C.30704@gmail.com> (raw)
In-Reply-To: <20091027021701.20826.67034.stgit@mimic.site>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
Patrick Mullaney wrote:
> The current code exhibits odd behavior in the guest when receiving L4RO
> packets. This was tracked down to the improper allocation of
> GFP_KERNEL memory from softirq context
>
Applied, thanks!
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
prev parent reply other threads:[~2009-10-27 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 2:17 [PATCH] vbus-enet: fix l4ro pool non-atomic allocations in softirq context Patrick Mullaney
2009-10-27 21:37 ` Gregory Haskins [this message]
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=4AE7680C.30704@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmullaney@novell.com \
/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