From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-block@nongnu.org,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Max Reitz" <mreitz@redhat.com>
Subject: [PATCH 0/4] block/vvfat: Fix leaks and out of bounds writes
Date: Fri, 30 Apr 2021 18:25:15 +0200 [thread overview]
Message-ID: <20210430162519.271607-1-philmd@redhat.com> (raw)
The first 3 patches are trivial leak fixes, the last
one is a RFC since I have no clue about this code.
Johannes, you wrote this 18 years ago, do you still
remember? =)
Philippe Mathieu-Daudé (4):
block/vvfat: Fix leak of BDRVVVFATState::qcow_filename
block/vvfat: Fix leak of BDRVVVFATState::used_clusters
block/vvfat: Fix leak of mapping_t::path
block/vvfat: Avoid out of bounds write in create_long_filename()
block/vvfat.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
--
2.26.3
next reply other threads:[~2021-04-30 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 16:25 Philippe Mathieu-Daudé [this message]
2021-04-30 16:25 ` [PATCH 1/4] block/vvfat: Fix leak of BDRVVVFATState::qcow_filename Philippe Mathieu-Daudé
2021-05-03 13:14 ` Stefano Garzarella
2021-04-30 16:25 ` [PATCH 2/4] block/vvfat: Fix leak of BDRVVVFATState::used_clusters Philippe Mathieu-Daudé
2021-05-03 13:24 ` Stefano Garzarella
2021-04-30 16:25 ` [PATCH 3/4] block/vvfat: Fix leak of mapping_t::path Philippe Mathieu-Daudé
2021-05-07 16:17 ` Max Reitz
2021-04-30 16:25 ` [PATCH 4/4] block/vvfat: Avoid out of bounds write in create_long_filename() Philippe Mathieu-Daudé
2021-05-05 13:46 ` Eric Blake
2021-05-05 13:11 ` [PATCH 0/4] block/vvfat: Fix leaks and out of bounds writes Johannes Schindelin
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=20210430162519.271607-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=johannes.schindelin@gmx.de \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).