From: Amit Shah <amit.shah@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH v2 2/2] virtio: console: add locking around c_ovq operations
Date: Tue, 2 Apr 2013 10:56:06 +0530 [thread overview]
Message-ID: <20130402052606.GA15084@amit.redhat.com> (raw)
In-Reply-To: <87vc8935ej.fsf@rustcorp.com.au>
On (Sat) 30 Mar 2013 [14:28:28], Rusty Russell wrote:
> Amit Shah <amit.shah@redhat.com> writes:
> > When multiple ovq operations are being performed (lots of open/close
> > operations on virtio_console fds), the __send_control_msg() function can
> > get confused without locking.
> >
> > A simple recipe to cause badness is:
> > * create a QEMU VM with two virtio-serial ports
> > * in the guest, do
> > while true;do echo abc >/dev/vport0p1;done
> > while true;do echo edf >/dev/vport0p2;done
> >
> > In one run, this caused a panic in __send_control_msg(). In another, I
> > got
> >
> > virtio_console virtio0: control-o:id 0 is not a head!
>
> Both applied to my fixes branch, with CC: stable added.
>
> For future reference, I prefer you to put the CC: stable@kernel.org tag
> in if you think it's a stable candidate.
Will do,
Thanks
Amit
prev parent reply other threads:[~2013-04-02 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 11:00 [PATCH v2 0/2] virtio: console: add locking around control out-vq Amit Shah
2013-03-29 11:00 ` [PATCH v2 1/2] virtio: console: rename cvq_lock to c_ivq_lock Amit Shah
2013-03-29 11:04 ` Wanlong Gao
2013-03-29 11:00 ` [PATCH v2 2/2] virtio: console: add locking around c_ovq operations Amit Shah
2013-03-29 11:05 ` Wanlong Gao
2013-03-30 3:58 ` Rusty Russell
2013-04-02 5:26 ` Amit Shah [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=20130402052606.GA15084@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.