From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git misc
Date: Sat, 8 Feb 2020 19:03:29 +0000 [thread overview]
Message-ID: <20200208190329.GG23230@ZenIV.linux.org.uk> (raw)
bmap series from cmaiolino + getting rid of convolutions in
copy_mount_options() (a couple of copy_from_user() instead of
an the __get_user() crap)
The following changes since commit c79f46a282390e0f5b306007bf7b11a46d529538:
Linux 5.5-rc5 (2020-01-05 14:23:27 -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 12efec5602744c5a185049eb4fcfd9aebe01bd6f:
saner copy_mount_options() (2020-02-03 21:23:33 -0500)
----------------------------------------------------------------
Al Viro (1):
saner copy_mount_options()
Carlos Maiolino (5):
fs: Enable bmap() function to properly return errors
cachefiles: drop direct usage of ->bmap method.
ecryptfs: drop direct calls to ->bmap
fibmap: Use bmap instead of ->bmap method in ioctl_fibmap
fibmap: Reject negative block numbers
drivers/md/md-bitmap.c | 16 ++++++++++------
fs/cachefiles/rdwr.c | 27 ++++++++++++++-------------
fs/ecryptfs/mmap.c | 16 ++++++----------
fs/f2fs/data.c | 16 +++++++++++-----
fs/inode.c | 32 +++++++++++++++++++-------------
fs/ioctl.c | 33 +++++++++++++++++++++++----------
fs/jbd2/journal.c | 22 +++++++++++++++-------
fs/namespace.c | 49 +++++++------------------------------------------
include/linux/fs.h | 9 ++++++++-
mm/page_io.c | 11 +++++++----
10 files changed, 120 insertions(+), 111 deletions(-)
next reply other threads:[~2020-02-08 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 19:03 Al Viro [this message]
2020-02-08 21:55 ` [git pull] vfs.git misc pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-07-19 3:46 Al Viro
2019-07-19 19: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=20200208190329.GG23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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