From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Pierre Morel <pmorel@linux.ibm.com>,
Michael Mueller <mimu@linux.ibm.com>,
linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: bfu@redhat.com, Vineeth Vijayan <vneethv@linux.ibm.com>
Subject: Re: [PATCH 1/1] virtio/s390: fix vritio-ccw device teardown
Date: Thu, 16 Sep 2021 00:00:39 +0200 [thread overview]
Message-ID: <20210916000039.7aebfe1a.pasic@linux.ibm.com> (raw)
In-Reply-To: <20210915215742.1793314-1-pasic@linux.ibm.com>
s/vritio/virtio/
(subject)
[..]
On Wed, 15 Sep 2021 23:57:42 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:
> Since commit 48720ba56891 ("virtio/s390: use DMA memory for ccw I/O and
> classic notifiers") we were supposed to make sure that
> virtio_ccw_release_dev() completes before the ccw device, and the
> attached dma pool are torn down, but unfortunately we did not.
> Before that commit it used to be OK to delay cleaning up the memory
> allocated by virtio-ccw indefinitely (which isn't really intuitive for
> guys used to destruction happens in reverse construction order).
>
[..]
WARNING: multiple messages have this Message-ID (diff)
From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Pierre Morel <pmorel@linux.ibm.com>,
Michael Mueller <mimu@linux.ibm.com>,
linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: bfu@redhat.com, Vineeth Vijayan <vneethv@linux.ibm.com>
Subject: Re: [PATCH 1/1] virtio/s390: fix vritio-ccw device teardown
Date: Thu, 16 Sep 2021 00:00:39 +0200 [thread overview]
Message-ID: <20210916000039.7aebfe1a.pasic@linux.ibm.com> (raw)
In-Reply-To: <20210915215742.1793314-1-pasic@linux.ibm.com>
s/vritio/virtio/
(subject)
[..]
On Wed, 15 Sep 2021 23:57:42 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:
> Since commit 48720ba56891 ("virtio/s390: use DMA memory for ccw I/O and
> classic notifiers") we were supposed to make sure that
> virtio_ccw_release_dev() completes before the ccw device, and the
> attached dma pool are torn down, but unfortunately we did not.
> Before that commit it used to be OK to delay cleaning up the memory
> allocated by virtio-ccw indefinitely (which isn't really intuitive for
> guys used to destruction happens in reverse construction order).
>
[..]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-09-15 22:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 21:57 [PATCH 1/1] virtio/s390: fix vritio-ccw device teardown Halil Pasic
2021-09-15 21:57 ` Halil Pasic
2021-09-15 22:00 ` Halil Pasic [this message]
2021-09-15 22:00 ` Halil Pasic
2021-09-16 8:59 ` Cornelia Huck
2021-09-16 8:59 ` Cornelia Huck
2021-09-16 13:18 ` Halil Pasic
2021-09-16 13:18 ` Halil Pasic
2021-09-17 8:40 ` Cornelia Huck
2021-09-17 8:40 ` Cornelia Huck
2021-09-19 22:39 ` Halil Pasic
2021-09-19 22:39 ` Halil Pasic
2021-09-20 7:41 ` Vineeth Vijayan
2021-09-20 10:07 ` Cornelia Huck
2021-09-20 10:07 ` Cornelia Huck
2021-09-21 3:25 ` Halil Pasic
2021-09-21 3:25 ` Halil Pasic
2021-09-21 12:09 ` Cornelia Huck
2021-09-21 12:09 ` Cornelia Huck
2021-09-21 13:31 ` Vineeth Vijayan
2021-09-21 16:52 ` Halil Pasic
2021-09-21 16:52 ` Halil Pasic
2021-09-21 18:25 ` Vineeth Vijayan
2021-09-20 10:30 ` Cornelia Huck
2021-09-20 10:30 ` Cornelia Huck
2021-09-20 13:27 ` Halil Pasic
2021-09-20 13:27 ` Halil Pasic
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=20210916000039.7aebfe1a.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=bfu@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mimu@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vneethv@linux.ibm.com \
/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.