All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Popov <alex.popov@linux.com>
To: John Snow <jsnow@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	qemu-stable@nongnu.org, mst@redhat.com, pmatouse@redhat.com,
	sstabellini@kernel.org, mdroth@linux.vnet.ibm.com,
	pjp@redhat.com
Subject: Re: [Qemu-devel] [QEMU-SECURITY] ide: fix assertion in ide_dma_cb() to prevent qemu DoS from quest
Date: Fri, 26 Jul 2019 23:09:36 +0200	[thread overview]
Message-ID: <781B2374-635B-4B24-AF3C-EA42152C2335@linux.com> (raw)
In-Reply-To: <76881947-141b-0a16-c52d-a315203c32eb@redhat.com>



26 июля 2019 г. 2:25:03 GMT+02:00, John Snow <jsnow@redhat.com> пишет:
>Oh, this is fun.
... 
>I can worry about a proper fix for 4.2+.

Hello John, 

Thanks for your letter. 

I double-checked the git history and mailing list, I'm still sure
that my fix for this assertion is correct.

You know this code very well, of course it would be great if you
prepare the further fixes. 

Feel free to add me to CC, I can review the patches and test
them with fuzzing. 

Best regards, 
Alexander


  reply	other threads:[~2019-07-26 21:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 14:07 [Qemu-devel] [QEMU-SECURITY] ide: fix assertion in ide_dma_cb() to prevent qemu DoS from quest Alexander Popov
2019-07-05 14:13 ` Alexander Popov
2019-07-15 11:24 ` Alexander Popov
2019-07-16 11:25   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-07-16 14:57     ` John Snow
2019-07-16 16:18       ` P J P
2019-07-26  0:25 ` [Qemu-devel] " John Snow
2019-07-26 21:09   ` Alexander Popov [this message]
2019-11-06 12:05   ` Michael S. Tsirkin
2019-11-06 22:05     ` Alexander Popov
2019-11-14 17:31       ` Alexander Popov
2019-11-06 10:17 ` Alexander Popov
2019-11-06 12:08   ` Michael S. Tsirkin
2019-11-06 22:01     ` Alexander Popov

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=781B2374-635B-4B24-AF3C-EA42152C2335@linux.com \
    --to=alex.popov@linux.com \
    --cc=jsnow@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=pjp@redhat.com \
    --cc=pmatouse@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=sstabellini@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 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.