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 fixes
Date: Sun, 17 Jan 2021 03:21:15 +0000 [thread overview]
Message-ID: <20210117032115.GG3579531@ZenIV.linux.org.uk> (raw)
Several assorted fixes. I still think that audit ->d_name race
is better fixed that way for the benefit of backports, with any fancier
variants done on top of that.
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to d36a1dd9f77ae1e72da48f4123ed35627848507d:
dump_common_audit_data(): fix racy accesses to ->d_name (2021-01-16 15:11:35 -0500)
----------------------------------------------------------------
Al Viro (2):
umount(2): move the flag validity checks first
dump_common_audit_data(): fix racy accesses to ->d_name
Christoph Hellwig (1):
iov_iter: fix the uaccess area in copy_compat_iovec_from_user
fs/namespace.c | 7 +++++--
lib/iov_iter.c | 2 +-
security/lsm_audit.c | 7 +++++--
3 files changed, 11 insertions(+), 5 deletions(-)
next reply other threads:[~2021-01-17 3:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 3:21 Al Viro [this message]
2021-01-17 20:20 ` [git pull] vfs.git fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-25 6:59 Al Viro
2024-02-25 17:58 ` pr-tracker-bot
2023-03-10 20:27 Al Viro
2023-03-11 4:52 ` pr-tracker-bot
2020-10-11 18:06 Al Viro
2020-10-11 18:23 ` pr-tracker-bot
2020-04-28 21:18 Al Viro
2020-04-28 21:45 ` pr-tracker-bot
2020-03-12 22:37 Al Viro
2020-03-12 23:00 ` pr-tracker-bot
2020-02-24 0:22 Al Viro
2020-02-24 20:25 ` pr-tracker-bot
2020-01-26 18:25 Al Viro
2020-01-26 19:30 ` pr-tracker-bot
2019-11-24 20:05 Al Viro
2019-11-25 0:35 ` pr-tracker-bot
2019-11-15 0:50 Al Viro
2019-11-15 17:35 ` pr-tracker-bot
2019-05-05 2:18 Al Viro
2019-05-05 22:10 ` pr-tracker-bot
2019-03-03 3:42 Al Viro
2019-03-03 20:21 ` Linus Torvalds
2019-03-04 21:30 ` pr-tracker-bot
2018-11-30 5:15 Al Viro
2018-11-30 21:00 ` pr-tracker-bot
2018-08-12 17:44 Al Viro
2018-05-21 18:39 Al Viro
2018-05-21 18:59 ` Linus Torvalds
2018-03-16 1:41 Al Viro
2017-10-22 0:12 Al Viro
2017-10-11 4:54 Al Viro
2017-10-11 17:47 ` Vitaly Mayatskikh
2017-05-21 17:24 Al Viro
2017-04-27 7:34 Al Viro
2016-07-12 5:16 Al Viro
2016-07-01 20:51 Al Viro
2015-12-06 17:40 Al Viro
2015-11-25 23:08 Al Viro
2015-01-25 2:39 Al Viro
2014-11-22 4:43 Al Viro
2014-11-06 5:04 Al Viro
2013-11-11 16:30 [git pull] vfs.git Al Viro
2013-11-13 13:17 ` [git pull] vfs.git fixes 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=20210117032115.GG3579531@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.