From: Jeff Layton <jlayton@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: dwysocha@redhat.com, linux-cachefs@redhat.com,
v9fs-developer@lists.sourceforge.net,
linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] netfs: Fixes for the netfs lib
Date: Wed, 07 Apr 2021 16:36:14 -0400 [thread overview]
Message-ID: <0df4fd45c51dd8e87aa2a0869d81c39c9af83b31.camel@kernel.org> (raw)
In-Reply-To: <161781041339.463527.18139104281901492882.stgit@warthog.procyon.org.uk>
On Wed, 2021-04-07 at 16:46 +0100, David Howells wrote:
> Hi Jeff,
>
> Here's a bunch of fixes plus a tracepoint for the netfs library. I'm going
> to roll them into other patches, but I'm posting them here for separate
> review.
>
> David
> ---
> David Howells (5):
> netfs: Fix a missing rreq put in netfs_write_begin()
> netfs: Call trace_netfs_read() after ->begin_cache_operation()
> netfs: Don't record the copy termination error
> netfs: Fix copy-to-cache amalgamation
> netfs: Add a tracepoint to log failures that would be otherwise unseen
>
>
> fs/cachefiles/io.c | 17 ++++++++++
> fs/netfs/read_helper.c | 58 +++++++++++++++++++---------------
> include/linux/netfs.h | 6 ++++
> include/trace/events/netfs.h | 60 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 116 insertions(+), 25 deletions(-)
>
>
Thanks David,
I rebased onto your branch and gave ceph a spin with fscache and it all
worked fine. Let me know when you get those rolled into your branch and
I'll rebase the ceph/testing branch on top of it.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2021-04-07 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:46 [PATCH 0/5] netfs: Fixes for the netfs lib David Howells
2021-04-07 15:47 ` [PATCH 1/5] netfs: Fix a missing rreq put in netfs_write_begin() David Howells
2021-04-07 15:47 ` [PATCH 2/5] netfs: Call trace_netfs_read() after ->begin_cache_operation() David Howells
2021-04-07 15:47 ` [PATCH 3/5] netfs: Don't record the copy termination error David Howells
2021-04-07 15:47 ` [PATCH 4/5] netfs: Fix copy-to-cache amalgamation David Howells
2021-04-07 15:48 ` [PATCH 5/5] netfs: Add a tracepoint to log failures that would be otherwise unseen David Howells
2021-04-07 20:36 ` Jeff Layton [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=0df4fd45c51dd8e87aa2a0869d81c39c9af83b31.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=dwysocha@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).