From: Alexander Popov <alex.popov@linux.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
sstabellini@kernel.org, pmatouse@redhat.com,
mdroth@linux.vnet.ibm.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, qemu-stable@nongnu.org,
Kashyap Chamarthy <kashyap.cv@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
pjp@redhat.com
Subject: Re: [QEMU-SECURITY] ide: fix assertion in ide_dma_cb() to prevent qemu DoS from quest
Date: Thu, 7 Nov 2019 01:01:40 +0300 [thread overview]
Message-ID: <0de2309d-a913-b962-f6aa-1b03ee16dc03@linux.com> (raw)
In-Reply-To: <20191106070530-mutt-send-email-mst@kernel.org>
On 06.11.2019 15:08, Michael S. Tsirkin wrote:
> On Wed, Nov 06, 2019 at 01:17:51PM +0300, Alexander Popov wrote:
>> On 27.07.2019 00:09, Alexander Popov wrote:
>>> On 26.07.2019 2:25:03 GMT+02:00, John Snow <jsnow@redhat.com> wrote:
>>>> 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.
>>
>> Hello!
>>
>> I'm pointing politely to this issue again.
>>
>> It crashes qemu during syzkaller fuzzing.
>>
>> It's really annoying to manually apply the fix against it to qemu.
>
> I understand. Maybe the fuzzer can be taught to skip the
> specific issue for now?
Michael, thanks for your reply.
Yes, of course. You just forbid the fuzzer to use /dev/sg in the guest.
But I would rather fix the issue.
--
Best regards,
Alexander
prev parent reply other threads:[~2019-11-06 22:04 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
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 [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=0de2309d-a913-b962-f6aa-1b03ee16dc03@linux.com \
--to=alex.popov@linux.com \
--cc=aarcange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kashyap.cv@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@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 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).