qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>, Jason Andryuk <jandryuk@gmail.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PULL 3/4] 9pfs/xen: Fix segfault on shutdown
Date: Tue, 16 May 2023 23:34:15 +0300	[thread overview]
Message-ID: <b45f888c-245f-ff39-aead-0bbbf53bb248@msgid.tls.msk.ru> (raw)
In-Reply-To: <92e667f6fd5806a6a705a2a43e572bd9ec6819da.1684250463.git.qemu_oss@crudebyte.com>

16.05.2023 18:21, Christian Schoenebeck wrote:
> From: Jason Andryuk <jandryuk@gmail.com>
> 
> xen_9pfs_free can't use gnttabdev since it is already closed and NULL-ed
> out when free is called.  Do the teardown in _disconnect().  This
> matches the setup done in _connect().
> 
> trace-events are also added for the XenDevOps functions.

This, while somewhat big, still smells like a stable-8.0 (and stable-7.2) material.

/mjt


  reply	other threads:[~2023-05-16 20:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 15:21 [PULL 0/4] 9p queue 2023-05-16 Christian Schoenebeck
2023-05-16 15:21 ` [PULL 4/4] configure: make clear that VirtFS is 9p Christian Schoenebeck
2023-05-16 15:21 ` [PULL 1/4] Don't require libcap-ng for virtfs support Christian Schoenebeck
2023-05-16 15:21 ` [PULL 2/4] tests/9p: fix potential leak in v9fs_rreaddir() Christian Schoenebeck
2023-05-16 15:21 ` [PULL 3/4] 9pfs/xen: Fix segfault on shutdown Christian Schoenebeck
2023-05-16 20:34   ` Michael Tokarev [this message]
2023-05-16 17:17 ` [PULL 0/4] 9p queue 2023-05-16 Richard Henderson
2023-05-16 17:22   ` Richard Henderson
2023-05-16 19:16 ` Richard Henderson

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=b45f888c-245f-ff39-aead-0bbbf53bb248@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=groug@kaod.org \
    --cc=jandryuk@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=qemu_oss@crudebyte.com \
    --cc=sstabellini@kernel.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).