From: Boaz Harrosh <boaz@plexistor.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Unexpected behavior from xarray - Is it expected?
Date: Tue, 14 Jul 2020 20:54:35 +0300 [thread overview]
Message-ID: <338db3b4-17cd-959b-3a45-8cf406cc8ed1@plexistor.com> (raw)
In-Reply-To: <20200714134627.GC12769@casper.infradead.org>
On 14/07/2020 16:46, Matthew Wilcox wrote:
> On Tue, Jul 14, 2020 at 02:24:18PM +0300, Boaz Harrosh wrote:
<>
>> But in the case that I have entered a *single* xa_store() *at index 0*, but then try
>> to GET a range 0-Y I get these unexpected results:
>> xas_next() will return the same entry repeatedly
>
> I thought this was fixed in commit 91abab83839aa2eba073e4a63c729832fdb27ea1
> Do you have that commit in your tree?
>
Haa! so so sorry. You are right I am on a Linux-v5.3 based tree and only
v5.4 contains this fix.
(I will carry the workaround for older Kernels on user-machines)
Sorry for the noise
Boaz
prev parent reply other threads:[~2020-07-14 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 11:24 Unexpected behavior from xarray - Is it expected? Boaz Harrosh
2020-07-14 13:17 ` Boaz Harrosh
2020-07-14 13:46 ` Matthew Wilcox
2020-07-14 17:54 ` Boaz Harrosh [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=338db3b4-17cd-959b-3a45-8cf406cc8ed1@plexistor.com \
--to=boaz@plexistor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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).