qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Florian Westphal <fw@strlen.de>,
	qemu-block@nongnu.org, eblake@redhat.com,
	vsementsov@yandex-team.ru, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] nbd/server: push pending frames after sending reply
Date: Fri, 24 Mar 2023 19:20:17 +0100	[thread overview]
Message-ID: <20230324182017.GB1871@breakpoint.cc> (raw)
In-Reply-To: <ZB3b4gw6FZHWvNz9@redhat.com>

Kevin Wolf <kwolf@redhat.com> wrote:
> Am 24.03.2023 um 11:47 hat Florian Westphal geschrieben:
> > +    qio_channel_set_cork(client->ioc, true);
> > +
> >      if (ret < 0) {
> >          /* It wasn't -EIO, so, according to nbd_co_receive_request()
> >           * semantics, we should return the error to the client. */
> > @@ -2692,6 +2694,7 @@ static coroutine_fn void nbd_trip(void *opaque)
> >          goto disconnect;
> >      }
> >  
> > +    qio_channel_set_cork(client->ioc, false);
> >  done:
> >      nbd_request_put(req);
> >      nbd_client_put(client);
> 
> In the error paths, we never call set_cork(false) again. I suppose the
> reason that this is okay is because the next thing is actually that we
> close the socket?

Yes, no need to uncork before close.


  reply	other threads:[~2023-03-24 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 10:47 [PATCH 1/1] nbd/server: push pending frames after sending reply Florian Westphal
2023-03-24 17:20 ` Kevin Wolf
2023-03-24 18:20   ` Florian Westphal [this message]
2023-03-24 19:43     ` Eric Blake
2023-03-24 19:41 ` Eric Blake
2023-03-24 20:03   ` [Libguestfs] " Eric Blake
2023-03-24 23:55     ` Florian Westphal
2023-03-27 11:44 ` Kevin Wolf

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=20230324182017.GB1871@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    /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).