From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: [Qemu-devel] [PULL 0/3] 9pfs fixes for 2.11 20170920
Date: Wed, 20 Sep 2017 15:50:35 +0200 [thread overview]
Message-ID: <20170920135038.21058-1-groug@kaod.org> (raw)
The following changes since commit c51700273ad9802a21c19f8d2b4bcb67c38e74ac:
Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20170919-v2' into staging (2017-09-19 18:08:48 +0100)
are available in the git repository at:
https://github.com/gkurz/qemu.git tags/for-upstream
for you to fetch changes up to 772a73692ecb52bace0cff6f95df62f59b8cabe0:
9pfs: check the size of transport buffer before marshaling (2017-09-20 08:48:52 +0200)
----------------------------------------------------------------
These patches fix regressions in 2.10
----------------------------------------------------------------
Jan Dakinevich (3):
9pfs: fix readdir() for 9p2000.u
9pfs: fix name_to_path assertion in v9fs_complete_rename()
9pfs: check the size of transport buffer before marshaling
hw/9pfs/9p.c | 60 ++++++++++++++++++++++++++++++------------------------------
1 file changed, 30 insertions(+), 30 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-20 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 13:50 Greg Kurz [this message]
2017-09-20 13:50 ` [Qemu-devel] [PULL 1/3] 9pfs: fix readdir() for 9p2000.u Greg Kurz
2017-09-20 13:50 ` [Qemu-devel] [PULL 2/3] 9pfs: fix name_to_path assertion in v9fs_complete_rename() Greg Kurz
2017-09-20 13:50 ` [Qemu-devel] [PULL 3/3] 9pfs: check the size of transport buffer before marshaling Greg Kurz
2017-09-20 21:03 ` [Qemu-devel] [PULL 0/3] 9pfs fixes for 2.11 20170920 Peter Maydell
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=20170920135038.21058-1-groug@kaod.org \
--to=groug@kaod.org \
--cc=peter.maydell@linaro.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).