From: Christoph Hellwig <hch@infradead.org>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: Kernel ops with flexfiles
Date: Tue, 6 Mar 2018 22:47:56 -0800 [thread overview]
Message-ID: <20180307064756.GA15922@infradead.org> (raw)
In-Reply-To: <1569515727.10818617.1520288819283.JavaMail.zimbra@desy.de>
FYI, I see very similar issues with blocklayout, also caused by the
refcount changes. But I didn't really didn't have any time to dig
into it yet.
next prev parent reply other threads:[~2018-03-07 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 22:26 Kernel ops with flexfiles Mkrtchyan, Tigran
2018-03-06 22:13 ` Mkrtchyan, Tigran
2018-03-07 6:47 ` Christoph Hellwig [this message]
2018-03-07 17:00 ` Mkrtchyan, Tigran
2018-03-07 20:09 ` Trond Myklebust
2018-03-07 20:56 ` Mkrtchyan, Tigran
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=20180307064756.GA15922@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
--cc=trond.myklebust@primarydata.com \
/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).