qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mrhines@linux.vnet.ibm.com
To: qemu-devel@nongnu.org
Cc: yamahata@private.email.ne.jp, aliguori@us.ibm.com,
	quintela@redhat.com, owasserm@redhat.com, mrhines@us.ibm.com,
	pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH for-1.6 0/4] rdma: additional cleanups, proper getaddrinfo() handling
Date: Wed,  7 Aug 2013 12:05:26 -0400	[thread overview]
Message-ID: <1375891530-13759-1-git-send-email-mrhines@linux.vnet.ibm.com> (raw)

From: "Michael R. Hines" <mrhines@us.ibm.com>

Some nice buffer-overrun checks and fixing incorrect usage of getaddrinfo()

Isaku Yamahata (3):
  rdma: use resp.len after validation in qemu_rdma_registration_stop
  rdma: validate RDMAControlHeader::len
  rdma: check if RDMAControlHeader::len match transferred byte

Michael R. Hines (1):
  rdma: proper getaddrinfo() handling

 migration-rdma.c |  100 ++++++++++++++++++++++++++++++++----------------------
 1 file changed, 59 insertions(+), 41 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2013-08-07 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 16:05 mrhines [this message]
2013-08-07 16:05 ` [Qemu-devel] [PATCH for-1.6 1/4] rdma: use resp.len after validation in qemu_rdma_registration_stop mrhines
2013-08-07 16:05 ` [Qemu-devel] [PATCH for-1.6 2/4] rdma: validate RDMAControlHeader::len mrhines
2013-08-07 16:05 ` [Qemu-devel] [PATCH for-1.6 3/4] rdma: check if RDMAControlHeader::len match transferred byte mrhines
2013-08-07 16:05 ` [Qemu-devel] [PATCH for-1.6 4/4] rdma: proper getaddrinfo() handling mrhines
2013-08-08  6:12   ` Orit Wasserman
2013-08-08 14:44     ` Michael R. Hines
2013-08-14 16:27 ` [Qemu-devel] [PATCH for-1.6 0/4] rdma: additional cleanups, " Anthony Liguori

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=1375891530-13759-1-git-send-email-mrhines@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yamahata@private.email.ne.jp \
    /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).