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 stuff
Date: Thu, 24 Dec 2020 23:35:07 +0000 [thread overview]
Message-ID: <20201224233507.GZ3579531@ZenIV.linux.org.uk> (raw)
Assorted patches from previous cycle(s)...
The following changes since commit b65054597872ce3aefbc6a666385eabdf9e288da:
Linux 5.10-rc6 (2020-11-29 15:50:50 -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 2e2cbaf920d14de9a96180ddefd6861bcc46f07d:
fix hostfs_open() use of ->f_path.dentry (2020-12-21 21:42:29 -0500)
----------------------------------------------------------------
Al Viro (2):
Make sure that make_create_in_sticky() never sees uninitialized value of dir_mode
fix hostfs_open() use of ->f_path.dentry
Eric Biggers (1):
fs/namespace.c: WARN if mnt_count has become negative
Hao Li (2):
fs: Handle I_DONTCACHE in iput_final() instead of generic_drop_inode()
fs: Kill DCACHE_DONTCACHE dentry even if DCACHE_REFERENCED is set
fs/dcache.c | 9 ++++++++-
fs/hostfs/hostfs_kern.c | 2 +-
fs/inode.c | 4 +++-
fs/namei.c | 4 +++-
fs/namespace.c | 9 ++++++---
fs/pnode.h | 2 +-
include/linux/fs.h | 3 +--
7 files changed, 23 insertions(+), 10 deletions(-)
next reply other threads:[~2020-12-24 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 23:35 Al Viro [this message]
2020-12-25 19:09 ` [git pull] vfs.git misc stuff pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-04-02 1:52 Al Viro
2022-04-02 3:07 ` pr-tracker-bot
2021-02-27 6:00 Al Viro
2021-02-27 16:21 ` Linus Torvalds
2021-02-27 17:18 ` Al Viro
2021-02-27 16:29 ` pr-tracker-bot
2017-05-09 5:34 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=20201224233507.GZ3579531@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.