From: P J P <ppandit@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
qemu-block@nongnu.org, Chensongnian <chensongnian@huawei.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v1] ide: check BlockBackend object in ide_cancel_dma_sync
Date: Tue, 18 Jul 2017 12:25:25 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1707181221260.2603@wniryva> (raw)
In-Reply-To: <20170717160503.GL5301@noname.redhat.com>
Hello Kevin,
+-- On Mon, 17 Jul 2017, Kevin Wolf wrote --+
| I think Stefan didn't only mean a stack trace, but an actual instruction
| how to reproduce this. VM configuration, what actions to take, etc.
|
| In fact, I will add that we will probably want a qtest case as a
| regression test anyway, and tests are always great for describing how to
| reproduce a problem, too.
It was found via a fuzzing exercise; I've requested a reproducer from original
reporter, will try to create a qtest once it's available.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
prev parent reply other threads:[~2017-07-18 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:01 [Qemu-devel] [PATCH v1] ide: check BlockBackend object in ide_cancel_dma_sync P J P
2017-07-17 16:05 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-07-18 6:55 ` P J P [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=alpine.LFD.2.20.1707181221260.2603@wniryva \
--to=ppandit@redhat.com \
--cc=chensongnian@huawei.com \
--cc=kwolf@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 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).