From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Martyn Welch <martyn@collabora.com>,
Richard Weinberger <richard@nod.at>,
Jeff Dike <jdike@addtoit.com>,
linux-um <linux-um@lists.infradead.org>,
kernel@collabora.com,
Christopher Obbard <chris.obbard@collabora.com>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH] um: ubd: Submit all data segments atomically
Date: Sat, 21 Nov 2020 23:09:18 -0500 [thread overview]
Message-ID: <874klikp75.fsf@collabora.com> (raw)
In-Reply-To: <CAFLxGvwS6b5Ua9VBaOGS5iYZVd5rYFi=W_VBMxFj5hgSHk__Tw@mail.gmail.com> (Richard Weinberger's message of "Wed, 18 Nov 2020 22:46:14 +0100")
Richard Weinberger <richard.weinberger@gmail.com> writes:
> On Wed, Nov 18, 2020 at 10:19 PM Gabriel Krisman Bertazi
> <krisman@collabora.com> wrote:
>>
>> Anton Ivanov <anton.ivanov@cambridgegreys.com> writes:
>>
>> > On 25/10/2020 04:41, Gabriel Krisman Bertazi wrote:
>> >> Internally, UBD treats each physical IO segment as a separate command to
>> >> be submitted in the execution pipe. If the pipe returns a transient
>> >> error after a few segments have already been written, UBD will tell the
>> >> block layer to requeue the request, but there is no way to reclaim the
>> >> segments already submitted. When a new attempt to dispatch the request
>> >> is done, those segments already submitted will get duplicated, causing
>> >> the WARN_ON below in the best case, and potentially data corruption.
>> >> In my system, running a UML instance with 2GB of RAM and a 50M UBD
>> >> disk,
>>
>> >> [...]
>> >> ---[ end trace c6e7444e55386c0f ]---
>> >> Cc: Christopher Obbard <chris.obbard@collabora.com>
>> >> Reported-by: Martyn Welch <martyn@collabora.com>
>> >> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
>>
>> > Acked-By: Anton Ivanov <anton.ivanov@cambridgegreys.com>
>>
>> Hi,
>>
>> Is this queued somewhere? I've been watching the linux-next branch of
>
> I had only one minor comment but apparently the mail got stuck locally. :-(
> Just sent my mail again.
Thanks for the feedback. I fixed up the array declaration and I'm just
completing it a new round of test before sending the v2.
--
Gabriel Krisman Bertazi
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2020-11-22 4:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 4:41 [PATCH] um: ubd: Submit all data segments atomically Gabriel Krisman Bertazi
2020-10-26 9:25 ` Anton Ivanov
2020-11-18 21:19 ` Gabriel Krisman Bertazi
2020-11-18 21:46 ` Richard Weinberger
2020-11-22 4:09 ` Gabriel Krisman Bertazi [this message]
2020-10-26 11:52 ` Christopher Obbard
2020-11-18 21:45 ` Richard Weinberger
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=874klikp75.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=chris.obbard@collabora.com \
--cc=jdike@addtoit.com \
--cc=kernel@collabora.com \
--cc=linux-um@lists.infradead.org \
--cc=martyn@collabora.com \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.