From: William Dauchy <william@gandi.net>
To: stable@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: kvm: irqchip: fix memory leak in -stable
Date: Wed, 4 Nov 2015 14:11:54 +0100 [thread overview]
Message-ID: <20151104131154.GI7714@gandi.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Hello stable release team,
The commit ba60c41 kvm: irqchip: fix memory leak
is fixing commit e73f61e kvm: irqchip: Break up high order allocations of kvm_irq_routing_table
I believe commit ba60c41 kvm: irqchip: fix memory leak
is a good candidate for -stable. I also got an agreement from Paolo.
Best regards,
--
William
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-11-04 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 13:11 William Dauchy [this message]
2015-11-06 6:48 ` kvm: irqchip: fix memory leak in -stable Greg KH
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=20151104131154.GI7714@gandi.net \
--to=william@gandi.net \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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;
as well as URLs for NNTP newsgroup(s).