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.4
Date: Fri, 27 Sep 2019 16:27:26 +0200 [thread overview]
Message-ID: <20190927142725.GA8169@nautica> (raw)
Hi Linus,
Some of the usual small fixes and cleanup.
I didn't get the target version wrong this time! :)
The following changes since commit 089cf7f6ecb266b6a4164919a2e69bd2f938374a:
Linux 5.3-rc7 (2019-09-02 09:57:40 -0700)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-5.4
for you to fetch changes up to aafee43b72863f1f70aeaf1332d049916e8df239:
9p/vfs_super.c: Remove unused parameter data in v9fs_fill_super
(2019-09-03 11:10:13 +0000)
----------------------------------------------------------------
9p pull request for inclusion in 5.4
Small fixes all around:
- avoid overlayfs copy-up for PRIVATE mmaps
- KUMSAN uninitialized warning for transport error
- one syzbot memory leak fix in 9p cache
- internal API cleanup for v9fs_fill_super
----------------------------------------------------------------
Bharath Vedartham (2):
9p/cache.c: Fix memory leak in v9fs_cache_session_get_cookie
9p/vfs_super.c: Remove unused parameter data in v9fs_fill_super
Chengguang Xu (1):
9p: avoid attaching writeback_fid on mmap with type PRIVATE
Lu Shuaibing (1):
9p: Transport error uninitialized
fs/9p/cache.c | 2 ++
fs/9p/vfs_file.c | 3 +++
fs/9p/vfs_super.c | 4 ++--
net/9p/client.c | 1 +
4 files changed, 8 insertions(+), 2 deletions(-)
Cheers,
--
Dominique | Asmadeus
next reply other threads:[~2019-09-27 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 14:27 Dominique Martinet [this message]
2019-09-27 23:00 ` [GIT PULL] 9p updates for 5.4 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=20190927142725.GA8169@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