From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL 00/12] 9p patches for 2.8 20161017
Date: Mon, 17 Oct 2016 17:17:18 +0100 [thread overview]
Message-ID: <CAFEAcA8-05Sw3kMSVm9NAmOErfuDLmrp27mT7xRTuJ+O5tWAig@mail.gmail.com> (raw)
In-Reply-To: <1476716754-26686-1-git-send-email-groug@kaod.org>
On 17 October 2016 at 16:05, Greg Kurz <groug@kaod.org> wrote:
> The following changes since commit ad728364e3916e1159ee94e5cd82b7a9c81d2dcc:
>
> Merge remote-tracking branch 'remotes/famz/tags/for-upstream' into staging (2016-10-17 11:56:18 +0100)
>
> are available in the git repository at:
>
> https://github.com/gkurz/qemu.git tags/for-upstream
>
> for you to fetch changes up to fdfcc9aeea1492f4b819a24c94dfb678145b1bf9:
>
> 9pfs: fix memory leak in v9fs_write (2016-10-17 14:13:58 +0200)
>
> ----------------------------------------------------------------
> This pull request contains:
> - a patch to add a vdc->reset() handler to virtio-9p
> - a bunch of patches to fix various memory leaks (thanks to Li Qiang)
> - some code cleanups for 9pfs
>
> ----------------------------------------------------------------
> Greg Kurz (6):
> 9pfs: fsdev: drop useless extern annotation for functions
> 9pfs: use coroutine_fn annotation in hw/9pfs/co*.[ch]
> 9pfs: use coroutine_fn annotation in hw/9pfs/9p.[ch]
> 9pfs: drop useless check in pdu_free()
> 9pfs: only free completed request if not flushed
> virtio-9p: add reset handler
>
> Li Qiang (6):
> 9pfs: allocate space for guest originated empty strings
> 9pfs: fix potential host memory leak in v9fs_read
> 9pfs: fix information leak in xattr read
> 9pfs: fix memory leak in v9fs_xattrcreate
> 9pfs: fix memory leak in v9fs_link
> 9pfs: fix memory leak in v9fs_write
Applied, thanks.
-- PMM
prev parent reply other threads:[~2016-10-17 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 15:05 [Qemu-devel] [PULL 00/12] 9p patches for 2.8 20161017 Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 01/12] 9pfs: allocate space for guest originated empty strings Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 02/12] 9pfs: fix potential host memory leak in v9fs_read Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 03/12] 9pfs: fsdev: drop useless extern annotation for functions Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 04/12] 9pfs: use coroutine_fn annotation in hw/9pfs/co*.[ch] Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 05/12] 9pfs: use coroutine_fn annotation in hw/9pfs/9p.[ch] Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 06/12] 9pfs: drop useless check in pdu_free() Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 07/12] 9pfs: only free completed request if not flushed Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 08/12] virtio-9p: add reset handler Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 09/12] 9pfs: fix information leak in xattr read Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 10/12] 9pfs: fix memory leak in v9fs_xattrcreate Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 11/12] 9pfs: fix memory leak in v9fs_link Greg Kurz
2016-10-17 15:05 ` [Qemu-devel] [PULL 12/12] 9pfs: fix memory leak in v9fs_write Greg Kurz
2016-10-17 16:17 ` Peter Maydell [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=CAFEAcA8-05Sw3kMSVm9NAmOErfuDLmrp27mT7xRTuJ+O5tWAig@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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).