From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] file locking changes for v5.6
Date: Fri, 06 Mar 2020 12:18:15 -0500 [thread overview]
Message-ID: <a14229cc7aabebfdffd405018d939d7a0ae1f1cd.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
The following changes since commit 98d54f81e36ba3bf92172791eba5ca5bd813989b:
Linux 5.6-rc4 (2020-03-01 16:38:46 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/filelock-v5.6-1
for you to fetch changes up to 6d390e4b5d48ec03bb87e63cf0a2bff5f4e116da:
locks: fix a potential use-after-free problem when wakeup a waiter (2020-03-06 11:54:13 -0500)
----------------------------------------------------------------
Just a couple of late-breaking patches for the file locking code. The
second patch (from yangerkun) fixes a rather nasty looking potential
use-after-free that should go to stable.
The other patch could technically wait for 5.7, but it's fairly
innocuous so I figured we might as well take it.
Thanks,
Jeff
----------------------------------------------------------------
Kees Cook (1):
fcntl: Distribute switch variables for initialization
yangerkun (1):
locks: fix a potential use-after-free problem when wakeup a waiter
fs/fcntl.c | 6 ++++--
fs/locks.c | 14 --------------
2 files changed, 4 insertions(+), 16 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2020-03-06 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 17:18 Jeff Layton [this message]
2020-03-06 21:00 ` [GIT PULL] file locking changes for v5.6 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=a14229cc7aabebfdffd405018d939d7a0ae1f1cd.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).