From: Matthew Wilcox <willy@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-mm@kvack.org, mgorman@suse.de
Subject: Re: Truncate regression due to commit 69b6c1319b6
Date: Thu, 29 Aug 2019 04:59:40 -0700 [thread overview]
Message-ID: <20190829115940.GD6590@bombadil.infradead.org> (raw)
In-Reply-To: <20190827132925.GA9061@quack2.suse.cz>
On Tue, Aug 27, 2019 at 03:29:25PM +0200, Jan Kara wrote:
> On Fri 31-05-19 12:04:31, Matthew Wilcox wrote:
> > On Thu, Mar 14, 2019 at 12:10:12PM +0100, Jan Kara wrote:
> > > On Thu 28-02-19 14:53:17, Matthew Wilcox wrote:
> > > > Here's what I'm currently looking at. xas_store() becomes a wrapper
> > > > around xas_replace() and xas_replace() avoids the xas_init_marks() and
> > > > xas_load() calls:
> > >
> > > This looks reasonable to me. Do you have some official series I could test
> > > or where do we stand?
> >
> > Hi Jan,
> >
> > Sorry for the delay; I've put this into the xarray tree:
> >
> > http://git.infradead.org/users/willy/linux-dax.git/shortlog/refs/heads/xarray
> >
> > I'm planning to ask Linus to pull it in about a week.
>
> Hum, I still don't see these xarray changes (the change to use
> xas_replace() in particular) upstream. What has happened?
It had a bug and I decided to pull the patch for now rather than find
the bug ... this regression is still on my mind. Thanks for the ping.
prev parent reply other threads:[~2019-08-29 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:56 Truncate regression due to commit 69b6c1319b6 Jan Kara
2019-02-26 17:27 ` Matthew Wilcox
2019-02-27 6:03 ` Nicholas Piggin
2019-02-27 12:35 ` Matthew Wilcox
2019-02-28 9:31 ` Nicholas Piggin
2019-02-27 11:27 ` Jan Kara
2019-02-27 12:24 ` Matthew Wilcox
2019-02-27 16:55 ` Jan Kara
2019-02-28 22:53 ` Matthew Wilcox
2019-03-14 11:10 ` Jan Kara
2019-05-31 19:04 ` Matthew Wilcox
2019-08-27 13:29 ` Jan Kara
2019-08-29 11:59 ` Matthew Wilcox [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=20190829115940.GD6590@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).