All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Cc: Amos Kong <akong@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sasha Levin <sasha.levin@oracle.com>
Subject: [PULL] virtio-next
Date: Thu, 12 Jun 2014 12:12:57 +0930	[thread overview]
Message-ID: <87oaxyq24u.fsf@rustcorp.com.au> (raw)

The following changes since commit ec6931b281797b69e6cf109f9cc94d5a2bf994e0:

  word-at-a-time: avoid undefined behaviour in zero_bytemask macro (2014-04-27 15:20:05 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus

for you to fetch changes up to c77fba9ab058d1e96ed51d4215e56905c9ef8d2a:

  virtio_scsi: don't call virtqueue_add_sgs(... GFP_NOIO) holding spinlock. (2014-05-21 11:25:41 +0930)

----------------------------------------------------------------
Main excitement is a virtio_scsi fix for alloc holding spinlock on the abort
path, which I refuse to CC stable since (1) I discovered it myself, and
(2) it's been there forever with no reports.

Cheers,
Rusty.
----------------------------------------------------------------
Amos Kong (1):
      virtio-rng: support multiple virtio-rng devices

Heinz Graalfs (1):
      virtio_ccw: introduce device_lost in virtio_ccw_device

Rusty Russell (2):
      virtio: virtio_break_device() to mark all virtqueues broken.
      virtio_scsi: don't call virtqueue_add_sgs(... GFP_NOIO) holding spinlock.

Sasha Levin (2):
      virtio-rng: fix boot with virtio-rng device
      virtio-rng: fixes for device registration/unregistration

 drivers/char/hw_random/virtio-rng.c | 105 +++++++++++++++++++++++-------------
 drivers/s390/kvm/virtio_ccw.c       |  49 ++++++++++++-----
 drivers/scsi/virtio_scsi.c          |  15 +++---
 drivers/virtio/virtio_ring.c        |  15 ++++++
 include/linux/virtio.h              |   2 +
 5 files changed, 127 insertions(+), 59 deletions(-)

             reply	other threads:[~2014-06-12  3:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  2:42 Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-18  5:15 [PULL] virtio-next Rusty Russell
2015-02-18  5:15 ` Rusty Russell
2014-08-11  2:28 Rusty Russell
2014-08-11  2:28 ` Rusty Russell
2014-04-01  2:58 Rusty Russell
2013-11-07 11:27 Rusty Russell
2013-07-10  3:39 Rusty Russell
2013-07-01  0:55 Rusty Russell
2012-12-18  5:16 Rusty Russell
2012-12-20  3:56 ` Rusty Russell

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=87oaxyq24u.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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.