From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] file locking changes for v6.0
Date: Mon, 01 Aug 2022 07:07:57 -0400 [thread overview]
Message-ID: <6dfd152d3643c568b928a96d334b50754cd752d4.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
The following changes since commit ff6992735ade75aae3e35d16b17da1008d753d28:
Linux 5.19-rc7 (2022-07-17 13:30:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/filelock-v6.0
for you to fetch changes up to db4abb4a32ec979ea5deea4d0095fa22ec99a623:
fs/lock: Rearrange ops in flock syscall. (2022-07-18 10:01:47 -0400)
----------------------------------------------------------------
Just a couple of flock() patches from Kuniyuki Iwashima. The main
changes are that this moves a file_lock allocation from the slab to the
stack.
----------------------------------------------------------------
Kuniyuki Iwashima (2):
fs/lock: Don't allocate file_lock in flock_make_lock().
fs/lock: Rearrange ops in flock syscall.
fs/locks.c | 77 ++++++++++++++++++++++++++++-------------------------------------------------
1 file changed, 28 insertions(+), 49 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:[~2022-08-01 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 11:07 Jeff Layton [this message]
2022-08-01 16:18 ` [GIT PULL] file locking changes for v6.0 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=6dfd152d3643c568b928a96d334b50754cd752d4.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kuniyu@amazon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).