From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: mreitz@redhat.com, kwolf@redhat.com, pbonzini@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH 5/5] block/nbd-client: don't check ioc
Date: Tue, 8 May 2018 09:36:53 +0300 [thread overview]
Message-ID: <26df9d70-4d26-5154-9fdb-ffb18951c4e7@virtuozzo.com> (raw)
In-Reply-To: <d061f619-d1f7-57be-d8f0-0792ca64504a@redhat.com>
07.05.2018 21:08, Eric Blake wrote:
> On 05/07/2018 10:44 AM, Vladimir Sementsov-Ogievskiy wrote:
>> We have several paranoiac checks for ioc != NULL. But ioc may become
>> NULL only on close, which should not happen during requests handling.
>> Also, we check ioc only sometimes, not after each yield, which is
>> inconsistent. Let's drop these checks.
>
> Can (or even should) any of these be replaced by asserts that ioc is
> not NULL?
>
>>
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>> ---
>> block/nbd-client.c | 14 +-------------
>> 1 file changed, 1 insertion(+), 13 deletions(-)
>
No problem, I can add them. Actually in most of cases we will crash very
soon on
next QIO_CHANNEL_GET_CLASS(ioc). The exclusions (looked through) are:
- "if (!s->ioc || s->quit) {" case, if reply is not simple.
- zero-length io requests in other cases, if they are possible
--
Best regards,
Vladimir
next prev parent reply other threads:[~2018-05-08 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:44 [Qemu-devel] [PATCH 0/5] NBD reconnect: preliminary refactoring Vladimir Sementsov-Ogievskiy
2018-05-07 15:44 ` [Qemu-devel] [PATCH 1/5] block/nbd-client: split channel errors from export errors Vladimir Sementsov-Ogievskiy
2018-05-07 15:44 ` [Qemu-devel] [PATCH 2/5] block/nbd: move connection code from block/nbd to block/nbd-client Vladimir Sementsov-Ogievskiy
2018-05-07 15:44 ` [Qemu-devel] [PATCH 3/5] block/nbd-client: split connection from initialization Vladimir Sementsov-Ogievskiy
2018-05-07 15:44 ` [Qemu-devel] [PATCH 4/5] block/nbd-client: fix nbd_reply_chunk_iter_receive Vladimir Sementsov-Ogievskiy
2018-05-07 15:44 ` [Qemu-devel] [PATCH 5/5] block/nbd-client: don't check ioc Vladimir Sementsov-Ogievskiy
2018-05-07 18:08 ` Eric Blake
2018-05-08 6:36 ` Vladimir Sementsov-Ogievskiy [this message]
2018-05-17 9:54 ` [Qemu-devel] [PATCH 0/5] NBD reconnect: preliminary refactoring Vladimir Sementsov-Ogievskiy
2018-05-17 13:48 ` Eric Blake
2018-05-18 11:32 ` Vladimir Sementsov-Ogievskiy
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=26df9d70-4d26-5154-9fdb-ffb18951c4e7@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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).