From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: "Eric Blake" <eblake@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"kraxel@redhat.com" <kraxel@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] util/qemu-sockets: fix keep_alive handling in inet_connect_saddr
Date: Wed, 25 Sep 2019 11:33:09 +0000 [thread overview]
Message-ID: <1296f8b0-b1db-3125-1989-47c4eed2b3e9@virtuozzo.com> (raw)
In-Reply-To: <00357f96-367e-d003-c166-d43083ee60af@virtuozzo.com>
11.09.2019 15:08, Vladimir Sementsov-Ogievskiy wrote:
> 10.09.2019 16:59, Eric Blake wrote:
>> On 9/10/19 3:03 AM, Daniel P. Berrangé wrote:
>>> On Tue, Sep 10, 2019 at 10:59:43AM +0300, Vladimir Sementsov-Ogievskiy wrote:
>>>> In "if (saddr->keep_alive) {" we may already be on error path, with
>>>> invalid sock < 0. Fix it by returning error earlier.
>>>>
>>>> Reported-by: Coverity (CID 1405300)
>>>> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
>>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>>> ---
>>>> util/qemu-sockets.c | 5 +++--
>>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>>
>> Thanks. Will queue through my NBD tree, since that's where the original
>> problem was introduced.
>>
>
> Please add when queueing:
>
> Fixes: aec21d31756cbd
>
Hmm, don't you forget? Don't see it neither in pull request nor in your branches.
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-09-25 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 7:59 [Qemu-devel] [PATCH] util/qemu-sockets: fix keep_alive handling in inet_connect_saddr Vladimir Sementsov-Ogievskiy
2019-09-10 8:03 ` Daniel P. Berrangé
2019-09-10 13:59 ` Eric Blake
2019-09-11 12:08 ` Vladimir Sementsov-Ogievskiy
2019-09-25 11:33 ` Vladimir Sementsov-Ogievskiy [this message]
2019-09-25 13:13 ` Eric Blake
2019-09-10 9:37 ` Stefano Garzarella
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=1296f8b0-b1db-3125-1989-47c4eed2b3e9@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=berrange@redhat.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.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).