From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] 9p for 5.20 (or 6.0)
Date: Sat, 6 Aug 2022 17:56:00 +0900 [thread overview]
Message-ID: <Yu4soPL07+/xDd3D@codewreck.org> (raw)
Hi Linus,
Note this will conflict with Al Viro's "9p: convert to advancing variant
of iov_iter_get_pages_alloc()" that I believe he hasn't sent yet, but it
should be simple enough to untangle.
I also had a few more improvements tested locally I forgot to push to
-next, so I guess they'll wait for next cycle :/ Sorry Christian...
The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:
Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-5.20
for you to fetch changes up to aa7aeee169480e98cf41d83c01290a37e569be6d:
net/9p: Initialize the iounit field during fid creation (2022-07-16 07:16:55 +0900)
----------------------------------------------------------------
9p-for-5.20
- a couple of fixes
- add a tracepoint for fid refcounting
- some cleanup/followup on fid lookup
- some cleanup around req refcounting
----------------------------------------------------------------
Dominique Martinet (4):
9p fid refcount: add p9_fid_get/put wrappers
9p fid refcount: add a 9p_fid_ref tracepoint
9p fid refcount: cleanup p9_fid_put calls
9p: roll p9_tag_remove into p9_req_put
Hangyu Hua (1):
net: 9p: fix refcount leak in p9_read_work() error handling
Kent Overstreet (2):
9p: Drop kref usage
9p: Add client parameter to p9_req_put()
Tyler Hicks (5):
9p: Track the root fid with its own variable during lookups
9p: Make the path walk logic more clear about when cloning is required
9p: Remove unnecessary variable for old fids while walking from d_parent
9p: Fix minor typo in code comment
net/9p: Initialize the iounit field during fid creation
Yang Li (1):
9p: Fix some kernel-doc comments
fs/9p/fid.c | 61 ++++++++++++++-----------
fs/9p/fid.h | 6 +--
fs/9p/vfs_addr.c | 4 +-
fs/9p/vfs_dentry.c | 4 +-
fs/9p/vfs_dir.c | 2 +-
fs/9p/vfs_file.c | 9 ++--
fs/9p/vfs_inode.c | 89 ++++++++++++++++---------------------
fs/9p/vfs_inode_dotl.c | 82 +++++++++++++---------------------
fs/9p/vfs_super.c | 8 ++--
fs/9p/xattr.c | 8 ++--
include/net/9p/client.h | 49 ++++++++++++++++++--
include/trace/events/9p.h | 48 ++++++++++++++++++++
net/9p/client.c | 168 +++++++++++++++++++++++++++++++++++----------------------------------
net/9p/trans_fd.c | 13 +++---
net/9p/trans_rdma.c | 2 +-
net/9p/trans_virtio.c | 4 +-
net/9p/trans_xen.c | 2 +-
17 files changed, 314 insertions(+), 245 deletions(-)
--
Dominique
next reply other threads:[~2022-08-06 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 8:56 Dominique Martinet [this message]
2022-08-06 22:08 ` [GIT PULL] 9p for 5.20 (or 6.0) pr-tracker-bot
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=Yu4soPL07+/xDd3D@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.