From: Jan Kara <jack@suse.cz>
To: torvalds@suse.cz
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Misc fs updates for 4.17-rc2
Date: Thu, 19 Apr 2018 11:42:17 +0200 [thread overview]
Message-ID: <20180419094217.5hrk4zrbftepgs25@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_4.17-rc2
to get:
* isofs memory leak fix
* two fsnotify fixes of event mask handling
* udf fix of UTF-16 handling
* couple other smaller cleanups
Note that I've experimentally created this pull request with a signed tag.
Please speak up if I did anything wrong.
Top of the tree is 44f06ba8297c. The full shortlog is:
Amir Goldstein (4):
fanotify: fix logic of events on child
fsnotify: fix ignore mask logic in send_to_group()
fsnotify: fix typo in a comment about mark->g_list
MAINTAINERS: add an entry for FSNOTIFY infrastructure
Chengguang Xu (1):
isofs: fix potential memory leak in mount option parsing
Jan Kara (1):
udf: Fix leak of UTF-16 surrogates into encoded strings
Jia-Ju Bai (1):
fs: quota: Replace GFP_ATOMIC with GFP_KERNEL in dquot_init
Kyle Spiers (1):
isofs compress: Remove VLA usage
Souptick Joarder (1):
fs: ext2: Adding new return type vm_fault_t
The diffstat is
MAINTAINERS | 8 ++++++++
fs/ext2/file.c | 4 ++--
fs/isofs/compress.c | 19 ++++++++++++++++---
fs/isofs/inode.c | 3 +++
fs/notify/fanotify/fanotify.c | 34 +++++++++++++++-------------------
fs/notify/fsnotify.c | 25 +++++++++++--------------
fs/quota/dquot.c | 2 +-
fs/udf/unicode.c | 6 ++++++
include/linux/fsnotify_backend.h | 2 +-
9 files changed, 63 insertions(+), 40 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2018-04-19 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 9:42 Jan Kara [this message]
2018-04-19 9:48 ` [GIT PULL] Misc fs updates for 4.17-rc2 Jan Kara
2018-04-19 9:49 Jan Kara
2018-04-20 16:05 ` Linus Torvalds
2018-04-22 0:03 ` Jan Kara
2018-04-22 1:20 ` Linus Torvalds
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=20180419094217.5hrk4zrbftepgs25@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@suse.cz \
/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).