All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: keith.busch@intel.com, mreitz@redhat.com,
	Paolo Bonzini <pbonzini@redhat.com>, P J P <ppandit@redhat.com>,
	qemu-block@nongnu.org, Qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] nvme: fix oob access issue(CVE-2018-16847)
Date: Tue, 13 Nov 2018 11:17:04 +0100	[thread overview]
Message-ID: <20181113101704.GB4830@localhost.localdomain> (raw)
In-Reply-To: <CAKXe6SL=6m5u1utFoJCG65ucuBeGTiuu8rA9wEj_X-tO1jHzEA@mail.gmail.com>

Am 13.11.2018 um 02:45 hat Li Qiang geschrieben:
> Ping.... what't the status of this patch.
> 
> I see Kevin's new pr doesn't contain this patch.

Oh, I thought you said that you wanted to fix this at a higher level so
that the problem is caught before even getting into nvme code? If you
don't, I can apply the patch for my next pull request.

Kevin

  reply	other threads:[~2018-11-13 10:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02  1:22 [Qemu-devel] [PATCH] nvme: fix oob access issue(CVE-2018-16847) Li Qiang
2018-11-02  7:51 ` Philippe Mathieu-Daudé
2018-11-02 10:54 ` Kevin Wolf
2018-11-02 15:00   ` Keith Busch
2018-11-02 15:22   ` Li Qiang
2018-11-02 15:42     ` Kevin Wolf
2018-11-05  1:49       ` Li Qiang
2018-11-02 15:40 ` Keith Busch
2018-11-05  1:56   ` Li Qiang
2018-11-13 18:26   ` Paolo Bonzini
2018-11-13  1:45 ` Li Qiang
2018-11-13 10:17   ` Kevin Wolf [this message]
2018-11-13 10:24     ` Li Qiang
2018-11-13 18:27     ` Paolo Bonzini
2018-11-14  1:38       ` Li Qiang
2018-11-14 15:44         ` Paolo Bonzini
2018-11-15  3:14           ` Li Qiang
2018-11-15 18:10             ` Paolo Bonzini

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=20181113101704.GB4830@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=keith.busch@intel.com \
    --cc=liq3ea@gmail.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.