From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, eblake@redhat.com,
vsementsov@virtuozzo.com, peter.maydell@linaro.org,
rvkagan@yandex-team.ru
Subject: [PULL 0/1] NBD fix for 6.0-rc3
Date: Mon, 12 Apr 2021 15:18:45 +0300 [thread overview]
Message-ID: <20210412121846.144565-1-vsementsov@virtuozzo.com> (raw)
The following changes since commit 555249a59e9cdd6b58da103aba5cf3a2d45c899f:
Merge remote-tracking branch 'remotes/ehabkost-gl/tags/x86-next-pull-request' into staging (2021-04-10 16:58:56 +0100)
are available in the Git repository at:
https://src.openvz.org/scm/~vsementsov/qemu.git tags/pull-nbd-2021-04-12
for you to fetch changes up to d3c278b689845558cd9811940436b28ae6afc5d7:
block/nbd: fix possible use after free of s->connect_thread (2021-04-12 11:56:03 +0300)
----------------------------------------------------------------
One fix of possible use-after-free in NBD block-driver for 6.0-rc3
----------------------------------------------------------------
Note: the tag is signed by a new key, as I've lost the old one. So,
now there are two keys with my name on http://keys.gnupg.net, the elder
is lost. I feel stupid about that :(. Anyway, both keys are not signed by
anybody except for myself. And this is my first pull-request to Qemu,
so, I think some kind of TOFU still applies.
Vladimir Sementsov-Ogievskiy (1):
block/nbd: fix possible use after free of s->connect_thread
block/nbd.c | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.29.2
next reply other threads:[~2021-04-12 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 12:18 Vladimir Sementsov-Ogievskiy [this message]
2021-04-12 12:18 ` [PULL 1/1] block/nbd: fix possible use after free of s->connect_thread Vladimir Sementsov-Ogievskiy
2021-04-12 15:48 ` [PULL 0/1] NBD fix for 6.0-rc3 Peter Maydell
2021-04-13 6:47 ` Vladimir Sementsov-Ogievskiy
2021-04-13 10:22 ` 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=20210412121846.144565-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rvkagan@yandex-team.ru \
/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).