From: Cornelia Huck <cohuck@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
farman@linux.ibm.com, pasic@linux.ibm.com
Subject: Re: [PATCH v1 1/1] vfio-ccw: Destroy kmem cache region on module exit
Date: Tue, 4 Jun 2019 17:44:43 +0200 [thread overview]
Message-ID: <20190604174443.6f29a87e.cohuck@redhat.com> (raw)
In-Reply-To: <c0f39039d28af39ea2939391bf005e3495d890fd.1559576250.git.alifm@linux.ibm.com>
On Mon, 3 Jun 2019 11:42:47 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:
> Free the vfio_ccw_cmd_region on module exit.
Fixes: d5afd5d135c8 ("vfio-ccw: add handling for async channel instructions")
>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> ---
>
> I guess I missed this earlier while reviewing, but should'nt
> we destroy the vfio_ccw_cmd_region on module exit, as well?
>
> drivers/s390/cio/vfio_ccw_drv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/s390/cio/vfio_ccw_drv.c b/drivers/s390/cio/vfio_ccw_drv.c
> index 66a66ac..9cee9f2 100644
> --- a/drivers/s390/cio/vfio_ccw_drv.c
> +++ b/drivers/s390/cio/vfio_ccw_drv.c
> @@ -299,6 +299,7 @@ static void __exit vfio_ccw_sch_exit(void)
> css_driver_unregister(&vfio_ccw_sch_driver);
> isc_unregister(VFIO_CCW_ISC);
> kmem_cache_destroy(vfio_ccw_io_region);
> + kmem_cache_destroy(vfio_ccw_cmd_region);
> destroy_workqueue(vfio_ccw_work_q);
> }
> module_init(vfio_ccw_sch_init);
Thanks, applied.
prev parent reply other threads:[~2019-06-04 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1559576250.git.alifm@linux.ibm.com>
2019-06-03 15:42 ` [PATCH v1 1/1] vfio-ccw: Destroy kmem cache region on module exit Farhan Ali
2019-06-04 6:03 ` Cornelia Huck
2019-06-04 15:44 ` Cornelia Huck [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=20190604174443.6f29a87e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox