From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Will Shiu <Will.Shiu@mediatek.com>,
jwilk@jwilk.net, Stas Sergeev <stsp2@yandex.ru>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [GIT PULL] file locking updates for v6.6
Date: Thu, 24 Aug 2023 12:19:00 -0400 [thread overview]
Message-ID: <be49e494a64fc983e87fd96a441a4f13a62d4362.camel@kernel.org> (raw)
[jlayton@tleilax linux]$ git request-pull 1ef6663a587b git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git filelock-v6.6
The following changes since commit 1ef6663a587ba3e57dc5065a477db1c64481eedd:
Merge tag 'tag-chrome-platform-for-v6.5' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux (2023-06-26 20:12:07 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/filelock-v6.6
for you to fetch changes up to 74f6f5912693ce454384eaeec48705646a21c74f:
locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock (2023-08-24 10:42:19 -0400)
----------------------------------------------------------------
Just a few patches in this cycle:
- new functionality for F_OFD_GETLK: requesting a type of F_UNLCK will find info about whatever lock happens to be first in the given range, regardless of type.
- an OFD lock selftest
- bugfix involving a UAF in a tracepoint
- comment typo fix
----------------------------------------------------------------
Jakub Wilk (1):
fs/locks: Fix typo
Stas Sergeev (2):
fs/locks: F_UNLCK extension for F_OFD_GETLK
selftests: add OFD lock tests
Will Shiu (1):
locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock
fs/locks.c | 27 ++++++++--
tools/testing/selftests/filelock/Makefile | 5 ++
tools/testing/selftests/filelock/ofdlocks.c | 132 ++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 159 insertions(+), 5 deletions(-)
create mode 100644 tools/testing/selftests/filelock/Makefile
create mode 100644 tools/testing/selftests/filelock/ofdlocks.c
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2023-08-24 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 16:19 Jeff Layton [this message]
2023-08-28 20:15 ` [GIT PULL] file locking updates for v6.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=be49e494a64fc983e87fd96a441a4f13a62d4362.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Will.Shiu@mediatek.com \
--cc=chuck.lever@oracle.com \
--cc=jwilk@jwilk.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stsp2@yandex.ru \
--cc=torvalds@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).