All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net
Subject: [GIT PULL] 9p update for 5.11-rc1
Date: Mon, 21 Dec 2020 10:48:28 +0100	[thread overview]
Message-ID: <20201221094828.GA6602@nautica> (raw)


Hi Linus,

here's this cycle's update, finally finished on some very old patches
(originally april 2015!) to allow fixing open-unlink-fgetattr pattern.

Thanks to Eric, Greg and Jianyong for the bulk of the work, and Dan for
static analysis fixes on -next.


The following changes since commit 3cea11cd5e3b00d91caf0b4730194039b45c5891:

  Linux 5.10-rc2 (2020-11-01 14:43:51 -0800)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-5.11-rc1

for you to fetch changes up to cfd1d0f524a87b7d6d14b41a14fa4cbe522cf8cc:

  9p: Remove unnecessary IS_ERR() check (2020-12-01 08:19:02 +0100)

----------------------------------------------------------------
9p for 5.11-rc1

- fix long-standing limitation on open-unlink-fop pattern
- add refcount to p9_fid (fixes the above and will allow for more
cleanups and simplifications in the future)

----------------------------------------------------------------
Dan Carpenter (2):
      9p: Uninitialized variable in v9fs_writeback_fid()
      9p: Remove unnecessary IS_ERR() check

Dominique Martinet (2):
      9p: apply review requests for fid refcounting
      9p: Fix writeback fid incorrectly being attached to dentry

Eric Van Hensbergen (1):
      fs/9p: fix create-unlink-getattr idiom

Greg Kurz (2):
      fs/9p: track open fids
      fs/9p: search open fids first

Jianyong Wu (1):
      9p: add refcount to p9_fid struct

 fs/9p/fid.c             | 65  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----
 fs/9p/fid.h             | 11 ++++++++++-
 fs/9p/vfs_dentry.c      |  2 ++
 fs/9p/vfs_dir.c         |  6 +++++-
 fs/9p/vfs_file.c        |  7 ++++---
 fs/9p/vfs_inode.c       | 47  ++++++++++++++++++++++++++++++++++++++---------
 fs/9p/vfs_inode_dotl.c  | 35 +++++++++++++++++++++++++++++------
 fs/9p/vfs_super.c       |  1 +
 fs/9p/xattr.c           | 16 +++++++++++++---
 include/net/9p/client.h |  7 +++++++
 net/9p/client.c         | 14 +++++++++-----
 11 files changed, 178 insertions(+), 33 deletions(-)

-- 
Dominique

             reply	other threads:[~2020-12-21  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21  9:48 Dominique Martinet [this message]
2020-12-21 18:46 ` [GIT PULL] 9p update for 5.11-rc1 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=20201221094828.GA6602@nautica \
    --to=asmadeus@codewreck.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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.