From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: sasha.levin@oracle.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] virtio_pci: fix DEBUG_KOBJECT_RELEASE
Date: Sun, 4 Jan 2015 18:21:00 +0200 [thread overview]
Message-ID: <20150104162100.GA8153@redhat.com> (raw)
In-Reply-To: <1420386340-7719-1-git-send-email-mst@redhat.com>
On Sun, Jan 04, 2015 at 06:02:13PM +0200, Michael S. Tsirkin wrote:
> This is based on Sasha's patch, with some tweaks.
>
Sasha, I would appreciate it if you can send
a Tested-by tag to confirm this + the del_vqs
idempotent patches are sufficient to address
all issues you have with 3.19.
> Michael S. Tsirkin (2):
> virtio_pci: device-specific release callback
> virtio_pci: document why we defer kfree
>
> Sasha Levin (1):
> virtio_pci: defer kfree until release callback
>
> drivers/virtio/virtio_pci_common.h | 1 -
> drivers/virtio/virtio_pci_common.c | 9 ---------
> drivers/virtio/virtio_pci_legacy.c | 12 +++++++++++-
> 3 files changed, 11 insertions(+), 11 deletions(-)
>
> --
> MST
>
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2015-01-04 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 16:02 [PATCH 0/3] virtio_pci: fix DEBUG_KOBJECT_RELEASE Michael S. Tsirkin
2015-01-04 16:02 ` [PATCH 1/3] virtio_pci: device-specific release callback Michael S. Tsirkin
2015-01-04 16:02 ` [PATCH 2/3] virtio_pci: defer kfree until " Michael S. Tsirkin
2015-01-04 16:02 ` [PATCH 3/3] virtio_pci: document why we defer kfree Michael S. Tsirkin
2015-01-04 16:21 ` Michael S. Tsirkin [this message]
2015-01-05 18:47 ` [PATCH 0/3] virtio_pci: fix DEBUG_KOBJECT_RELEASE Sasha Levin
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=20150104162100.GA8153@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--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 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).