From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] 9p updates for 5.1
Date: Sun, 17 Mar 2019 15:25:24 +0100 [thread overview]
Message-ID: <20190317142524.GA5136@nautica> (raw)
Hi Linus,
Here is a 9p update for 5.1; there honestly hasn't been much.
The memory leak fix has been commited rather recently because it was
sent fairly late, but it's simple enough that four days in -next should
be enough (that's why I waited till the last minute to send, sorry for
that - feel free to pick for rc2 if that makes a difference)
The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:
Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)
are available in the Git repository at:
git://github.com/martinetd/linux tags/9p-for-5.1
for you to fetch changes up to bb06c388fa20ae24cfe80c52488de718a7e3a53f:
9p/net: fix memory leak in p9_client_create (2019-03-13 11:50:04
+0100)
----------------------------------------------------------------
Pull request for inlusion in 5.1
Two fixes (leak on invalid mount argument and possible deadlock on
i_size update on 32bit smp) and a fall-through warning cleanup
----------------------------------------------------------------
Gustavo A. R. Silva (1):
9p: mark expected switch fall-through
Hou Tao (1):
9p: use inode->i_lock to protect i_size_write() under 32-bit
zhengbin (1):
9p/net: fix memory leak in p9_client_create
fs/9p/v9fs_vfs.h | 23 +++++++++++++++++++++--
fs/9p/vfs_file.c | 6 +++++-
fs/9p/vfs_inode.c | 23 +++++++++++------------
fs/9p/vfs_inode_dotl.c | 27 ++++++++++++++-------------
fs/9p/vfs_super.c | 4 ++--
net/9p/client.c | 2 +-
net/9p/trans_xen.c | 2 +-
7 files changed, 55 insertions(+), 32 deletions(-)
next reply other threads:[~2019-03-17 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 14:25 Dominique Martinet [this message]
2019-03-17 16:15 ` [GIT PULL] 9p updates for 5.1 Linus Torvalds
2019-03-18 0:04 ` Dominique Martinet
2019-03-17 16:45 ` 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=20190317142524.GA5136@nautica \
--to=asmadeus@codewreck.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 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).