public inbox for [email protected]
 help / color / mirror / Atom feed
From: Kyoko Senpai <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Muhammad Rizki <[email protected]>,
	 Dina Maulina <[email protected]>,
	"GNU/Weeb Mailing List" <[email protected]>
Subject: Re: Fix data corruption bug
Date: Fri, 18 Nov 2022 23:09:07 +0700	[thread overview]
Message-ID: <CADhTs3PeuWvhG91m-K++qVXsPHK6kvhrd9MceDmj=r8S_i-j8g@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qPNhJcRo72b1CXSfTi9QwSha-WjXTjLLtHb2HEgRyQ-eQ@mail.gmail.com>

On Fri, Nov 18, 2022 at 9:31 AM Alviro Iskandar Setiawan wrote:
> On Fri, Nov 18, 2022 at 12:27 AM Ammar Faizi wrote:
> > From: Ammar Faizi <[email protected]>
> > Subject: [PATCH] chnet: Fix data corruption when a read operation is pending
> >
> > When a read operation is pending, the @read_ret_ variable has to be
> > set to -EINPROGRESS. The current CHNetDelegate::__Read() method
> > doesn't do that. This situation makes the caller abort the request
> > because it doesn't see -EINPROGRESS from the return value. This bug
> > is reproducible on a slow network connection where __Read()
> > operation often results in a pending state.
> >
> > This bug is introduced in commit 77bbcc903899 ("chnet: Completely
> > refactor again").
> >
> > Fixes: 77bbcc903899 ("chnet: Completely refactor again")
> > Signed-off-by: Ammar Faizi <[email protected]>
>
> Reviewed-by: Alviro Iskandar Setiawan <[email protected]>

Reviewed-by: Gilang Fachrezy <[email protected]>

      reply	other threads:[~2022-11-18 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 17:27 Fix data corruption bug Ammar Faizi
2022-11-18  2:30 ` Alviro Iskandar Setiawan
2022-11-18 16:09   ` Kyoko Senpai [this message]

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='CADhTs3PeuWvhG91m-K++qVXsPHK6kvhrd9MceDmj=r8S_i-j8g@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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