From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: "Hervé Poussineau" <hpoussin@reactos.org>, qemu-devel@nongnu.org
Cc: Old World <qemu-ppc@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH for-2.5] mac_dbdma: always initialize channel field in DBDMA_channel
Date: Fri, 13 Nov 2015 16:04:48 +0000 [thread overview]
Message-ID: <56460A20.2040906@ilande.co.uk> (raw)
In-Reply-To: <1447363448-20405-1-git-send-email-hpoussin@reactos.org>
On 12/11/15 21:24, Hervé Poussineau wrote:
> dbdma_from_ch() uses channel field to return the right DBDMA object.
> Previous code was working if guest OS was only using registered DMA channels.
> However, it lead to QEMU crashes if guest OS was using unregistered DMA channels.
>
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
> ---
> hw/misc/macio/mac_dbdma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/misc/macio/mac_dbdma.c b/hw/misc/macio/mac_dbdma.c
> index 779683c..5ee8f02 100644
> --- a/hw/misc/macio/mac_dbdma.c
> +++ b/hw/misc/macio/mac_dbdma.c
> @@ -557,7 +557,6 @@ void DBDMA_register_channel(void *dbdma, int nchan, qemu_irq irq,
> DBDMA_DPRINTF("DBDMA_register_channel 0x%x\n", nchan);
>
> ch->irq = irq;
> - ch->channel = nchan;
> ch->rw = rw;
> ch->flush = flush;
> ch->io.opaque = opaque;
> @@ -753,6 +752,7 @@ void* DBDMA_init (MemoryRegion **dbdma_mem)
> for (i = 0; i < DBDMA_CHANNELS; i++) {
> DBDMA_io *io = &s->channels[i].io;
> qemu_iovec_init(&io->iov, 1);
> + s->channels[i].channel = i;
> }
>
> memory_region_init_io(&s->mem, NULL, &dbdma_ops, s, "dbdma", 0x1000);
>
Reviewed-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
This definitely prevents a host crash here, although it is possible to
argue whether or not an assert is more useful than a hang for developers.
David, can you queue this for ppc-next? It's not urgent but it would be
good not to have a potential host crash in 2.5.
Incidentally the QEMU iov can disappear from the io struct now since it
was only used for Alex's original alignment fixes for the macio code,
and it is probably more correct to move head_remainder and
tail_remainder into MACIOIDEState since DBDMA doesn't always involve
disk devices - but that can wait for another day...
ATB,
Mark.
prev parent reply other threads:[~2015-11-13 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:24 [Qemu-devel] [PATCH for-2.5] mac_dbdma: always initialize channel field in DBDMA_channel Hervé Poussineau
2015-11-13 16:04 ` Mark Cave-Ayland [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=56460A20.2040906@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=david@gibson.dropbear.id.au \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).