From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH 0/2] block: Fix Transaction leaks
Date: Wed, 5 May 2021 12:25:05 +0200 [thread overview]
Message-ID: <YJJygRJXGUTBh0OD@merkur.fritz.box> (raw)
In-Reply-To: <306a7acd-87a0-aa31-16cf-a0c00a281d6e@virtuozzo.com>
Am 04.05.2021 um 08:56 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 03.05.2021 14:05, Kevin Wolf wrote:
> > These are two follow-up fixes for Vladimir's "block: update graph
> > permissions update". The bugs were reported by Coverity.
> >
> > Kevin Wolf (2):
> > block: Fix Transaction leak in bdrv_root_attach_child()
> > block: Fix Transaction leak in bdrv_reopen_multiple()
> >
> > block.c | 9 +++++----
> > 1 file changed, 5 insertions(+), 4 deletions(-)
>
> I'll rebase my "[PATCH 0/6] block permission updated follow-up" on top
> of this.
Ok, thanks. I've applied this to my block branch now.
Kevin
prev parent reply other threads:[~2021-05-05 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 11:05 [PATCH 0/2] block: Fix Transaction leaks Kevin Wolf
2021-05-03 11:05 ` [PATCH 1/2] block: Fix Transaction leak in bdrv_root_attach_child() Kevin Wolf
2021-05-03 11:43 ` Vladimir Sementsov-Ogievskiy
2021-05-03 11:49 ` Max Reitz
2021-05-03 11:51 ` Vladimir Sementsov-Ogievskiy
2021-05-03 11:53 ` Max Reitz
2021-05-03 12:14 ` Vladimir Sementsov-Ogievskiy
2021-05-03 12:31 ` Vladimir Sementsov-Ogievskiy
2021-05-03 11:05 ` [PATCH 2/2] block: Fix Transaction leak in bdrv_reopen_multiple() Kevin Wolf
2021-05-03 11:40 ` Vladimir Sementsov-Ogievskiy
2021-05-03 12:41 ` Kevin Wolf
2021-05-03 13:09 ` Vladimir Sementsov-Ogievskiy
2021-05-03 14:33 ` Kevin Wolf
2021-05-04 6:52 ` Vladimir Sementsov-Ogievskiy
2021-05-04 6:51 ` Vladimir Sementsov-Ogievskiy
2021-05-04 6:56 ` [PATCH 0/2] block: Fix Transaction leaks Vladimir Sementsov-Ogievskiy
2021-05-05 10:25 ` Kevin Wolf [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=YJJygRJXGUTBh0OD@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).