qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>
Subject: [PULL 0/3] 9p queue 2021-09-02
Date: Thu, 02 Sep 2021 13:42:47 +0200	[thread overview]
Message-ID: <cover.1630582967.git.qemu_oss@crudebyte.com> (raw)

The following changes since commit 59a89510b62ec23dbeab8b02fa4e3526e353d8b6:

  Merge remote-tracking branch 'remotes/stefanberger/tags/pull-tpm-2021-09-01-1' into staging (2021-09-02 08:51:31 +0100)

are available in the Git repository at:

  https://github.com/cschoenebeck/qemu.git tags/pull-9p-20210902

for you to fetch changes up to f83df00900816476cca41bb536e4d532b297d76e:

  9pfs: fix crash in v9fs_walk() (2021-09-02 13:26:22 +0200)

----------------------------------------------------------------
9pfs: misc patches

* Fix an occasional crash when handling 'Twalk' requests.

* Two code cleanup patches.

----------------------------------------------------------------
Christian Schoenebeck (3):
      hw/9pfs: avoid 'path' copy in v9fs_walk()
      hw/9pfs: use g_autofree in v9fs_walk() where possible
      9pfs: fix crash in v9fs_walk()

 hw/9pfs/9p.c   | 15 +++++++--------
 hw/9pfs/coth.h |  4 +++-
 2 files changed, 10 insertions(+), 9 deletions(-)


             reply	other threads:[~2021-09-02 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 11:42 Christian Schoenebeck [this message]
2021-09-02 11:42 ` [PULL 1/3] hw/9pfs: avoid 'path' copy in v9fs_walk() Christian Schoenebeck
2021-09-02 11:42 ` [PULL 2/3] hw/9pfs: use g_autofree in v9fs_walk() where possible Christian Schoenebeck
2021-09-02 11:42 ` [PULL 3/3] 9pfs: fix crash in v9fs_walk() Christian Schoenebeck
2021-09-03 12:08 ` [PULL 0/3] 9p queue 2021-09-02 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=cover.1630582967.git.qemu_oss@crudebyte.com \
    --to=qemu_oss@crudebyte.com \
    --cc=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).