From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git #work.misc
Date: Mon, 11 Mar 2019 00:39:40 +0000 [thread overview]
Message-ID: <20190311003940.GH2217@ZenIV.linux.org.uk> (raw)
Assorted fixes (really no common topic here)
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up to 12e1e7af1a55b9f911025365af4c689b3933c22a:
vfs: Make __vfs_write() static (2019-02-22 00:30:05 -0500)
----------------------------------------------------------------
Aurelien Jarno (1):
vfs: fix preadv64v2 and pwritev64v2 compat syscalls with offset == -1
Christoph Hellwig (2):
orangefs: don't reinitialize result_mask in ->getattr
fs: move generic stat response attr handling to vfs_getattr_nosec
Geert Uytterhoeven (1):
vfs: Make __vfs_write() static
Jann Horn (2):
splice: don't merge into linked buffers
pipe: stop using ->can_merge
Varad Gautam (1):
fs/devpts: always delete dcache dentry-s in dput()
fs/devpts/inode.c | 1 +
fs/orangefs/inode.c | 7 ++-----
fs/pipe.c | 32 +++++++++++++++++++++++++++++---
fs/read_write.c | 10 ++++++++--
fs/splice.c | 8 ++++----
fs/stat.c | 12 +++++++-----
include/linux/pipe_fs_i.h | 8 +-------
kernel/relay.c | 1 -
kernel/trace/trace.c | 2 --
net/smc/smc_rx.c | 1 -
10 files changed, 52 insertions(+), 30 deletions(-)
next reply other threads:[~2019-03-11 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 0:39 Al Viro [this message]
2019-03-12 22:20 ` [git pull] vfs.git #work.misc pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-08-14 0:23 Al Viro
2022-08-14 0:39 ` Linus Torvalds
2022-08-14 0:39 ` pr-tracker-bot
2017-11-17 3:04 [git pull] vfs.git work.misc Al Viro
2016-05-18 18:40 [git pull] vfs.git#work.misc Al Viro
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=20190311003940.GH2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).