From: Kevin Wolf <kwolf@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH 4/6] sheepdog: don't leak socket file descriptor upon connection failure
Date: Fri, 17 Aug 2012 15:40:40 +0200 [thread overview]
Message-ID: <502E49D8.5010301@redhat.com> (raw)
In-Reply-To: <87ipch63z4.fsf@rho.meyering.net>
Am 17.08.2012 15:30, schrieb Jim Meyering:
> Kevin Wolf wrote:
>> Am 16.05.2012 15:07, schrieb Jim Meyering:
>>> From: Jim Meyering <meyering@redhat.com>
>>>
>>> Signed-off-by: Jim Meyering <meyering@redhat.com>
>>
>> Acked-by: Kevin Wolf <kwolf@redhat.com>
>
> Hi Kevin,
>
> AFAICS, only one of these 6 patches has been applied.
> From what I recall (it's been nearly 3mo), there was good
> feedback and I posted at least one V2 patch.
> For reference, here's the start of the series:
>
> http://marc.info/?l=qemu-devel&m=133717388221635&w=2
>
> Let me know if there's anything I can do to help.
Oh, that's bad. This series is spreads across several subsystems, so by
acking the sheepdog patch (the only block layer one) I was intending to
signal that I'm okay with merging it, but that I expect a "global
maintainer" to actually commit it.
Did all your other series get merged? There were a lot more patches with
small fixes and I can't see them in git master at all. I seem to
remember that they got delayed because you posted them late during the
last freeze, but obviously they should have been long committed now.
Anthony, what happened with these series? I think it makes sense to pull
them into -rc1 because all of them were bug fixes, even though mostly
minor ones.
Kevin
> Jim Meyering (5):
> qemu-ga: don't leak a file descriptor upon failed lockf
> linux-user: do_msgrcv: don't leak host_mb upon TARGET_EFAULT failure
> sheepdog: don't leak socket file descriptor upon connection failure
> arm-semi: don't leak 1KB user string lock buffer upon TARGET_SYS_OPEN
> softmmu-semi: fix lock_user* functions not to deref NULL upon OOM
>
> block/sheepdog.c | 1 +
> linux-user/syscall.c | 4 ++--
> qemu-ga.c | 3 +++
> softmmu-semi.h | 5 ++++-
> target-arm/arm-semi.c | 13 +++++++------
> 5 files changed, 17 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2012-08-17 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 13:07 [Qemu-devel] [PATCH 0/6] plug memory and file-descriptor leaks Jim Meyering
2012-05-16 13:07 ` [Qemu-devel] [PATCH 1/6] qcow2: don't leak buffer for unexpected qcow_version in header Jim Meyering
2012-05-21 10:57 ` Kevin Wolf
2012-05-21 11:06 ` [Qemu-devel] [PATCHv2 " Jim Meyering
2012-05-21 11:24 ` Kevin Wolf
2012-05-21 11:07 ` [Qemu-devel] [PATCH " Jim Meyering
2012-05-16 13:07 ` [Qemu-devel] [PATCH 2/6] qemu-ga: avoid unconditional lockfile file descriptor leak Jim Meyering
2012-05-16 18:15 ` Michael Roth
2012-05-16 20:17 ` Jim Meyering
2012-05-16 20:19 ` [Qemu-devel] [PATCHv2 2/6] qemu-ga: don't leak a file descriptor upon failed lockf Jim Meyering
2012-05-16 20:58 ` Michael Roth
2012-05-16 13:07 ` [Qemu-devel] [PATCH 3/6] linux-user: do_msgrcv: don't leak host_mb upon TARGET_EFAULT failure Jim Meyering
2012-05-16 13:21 ` Peter Maydell
2012-05-16 13:50 ` Jim Meyering
2012-05-16 13:52 ` [Qemu-devel] [PATCHv2 " Jim Meyering
2012-05-16 13:07 ` [Qemu-devel] [PATCH 4/6] sheepdog: don't leak socket file descriptor upon connection failure Jim Meyering
2012-05-21 11:00 ` Kevin Wolf
2012-08-17 13:30 ` Jim Meyering
2012-08-17 13:40 ` Kevin Wolf [this message]
2012-08-17 13:42 ` Jim Meyering
2012-05-16 13:08 ` [Qemu-devel] [PATCH 5/6] arm-semi: don't leak 1kb user string lock buffer upon TARGET_SYS_OPEN Jim Meyering
2012-05-16 13:15 ` Peter Maydell
2012-05-16 13:08 ` [Qemu-devel] [PATCH 6/6] softmmu-semi: fix lock_user* functions not to deref NULL upon OOM Jim Meyering
2012-05-19 7:13 ` Matthew Fernandez
2012-05-19 15:46 ` Peter Maydell
2012-05-24 14:46 ` Jim Meyering
2012-05-24 14:46 ` [Qemu-devel] [PATCH v2 " Jim Meyering
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=502E49D8.5010301@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jim@meyering.net \
--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).