From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] vfs.git fixes
Date: Fri, 10 Mar 2023 20:27:37 +0000 [thread overview]
Message-ID: <20230310202737.GV3390869@ZenIV> (raw)
fs/file.c one is a genuine missing speculation barrier in pick_file() (reachable
e.g. via close(2)); alpha one is strictly speaking not a bug fix, but only
because confusion between preempt_enable() and preempt_disable() is harmless
on architecture without CONFIG_PREEMPT. Looks like alpha.git picked the
wrong version of patch - that braino used to be there in early versions, but
it had been fixed quite a while ago... I've checked what ended up in mainline,
fortunately all other parts of commit match the latest variant in my tree.
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to 609d54441493c99f21c1823dfd66fa7f4c512ff4:
fs: prevent out-of-bounds array speculation when closing a file descriptor (2023-03-09 22:46:21 -0500)
----------------------------------------------------------------
pick_file() speculation fix + fix for alpha mis(merge,cherry-pick)
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (1):
alpha: fix lazy-FPU mis(merged/applied/whatnot)
Theodore Ts'o (1):
fs: prevent out-of-bounds array speculation when closing a file descriptor
arch/alpha/lib/fpreg.c | 4 ++--
fs/file.c | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2023-03-10 20:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 20:27 Al Viro [this message]
2023-03-11 4:52 ` [git pull] vfs.git fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 19:55 Al Viro
2024-08-02 16:53 ` pr-tracker-bot
2024-02-25 6:59 Al Viro
2024-02-25 17:58 ` pr-tracker-bot
2021-01-17 3:21 Al Viro
2021-01-17 20:20 ` 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=20230310202737.GV3390869@ZenIV \
--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.