mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: [GIT PULL] file locking changes for v6.3
Date: Thu, 16 Feb 2023 06:07:34 -0500	[thread overview]
Message-ID: <c56632e59e4c5b727619de7dd79db11d15bdca6f.camel@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3354 bytes --]

The following changes since commit 1fe4fd6f5cad346e598593af36caeadc4f5d4fa9:

  Merge tag 'xfs-6.2-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux (2023-01-08 12:11:45 -0600)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v6.3

for you to fetch changes up to c65454a947263dfdf482076388aaed60af84ca2f:

  fs: remove locks_inode (2023-01-11 06:52:43 -0500)

----------------------------------------------------------------
The main change here is that I've broken out most of the file locking
definitions into a new header file. I also went ahead and completed the
removal of locks_inode function.

Note that there was a minor merge conflict with the fuse tree reported
by Stephen Rothwell:

https://lore.kernel.org/lkml/20230127112640.6f55e705@canb.auug.org.au/T/

Cheers,
----------------------------------------------------------------
Jeff Layton (2):
      filelock: move file locking definitions to separate header file
      fs: remove locks_inode

 arch/arm/kernel/sys_oabi-compat.c |   1 +
 fs/9p/vfs_file.c                  |   1 +
 fs/afs/flock.c                    |  14 +-
 fs/afs/internal.h                 |   1 +
 fs/attr.c                         |   1 +
 fs/ceph/caps.c                    |   1 +
 fs/ceph/locks.c                   |   1 +
 fs/cifs/cifsfs.c                  |   1 +
 fs/cifs/cifsglob.h                |   1 +
 fs/cifs/cifssmb.c                 |   1 +
 fs/cifs/file.c                    |   1 +
 fs/cifs/smb2file.c                |   1 +
 fs/dlm/plock.c                    |   1 +
 fs/fcntl.c                        |   1 +
 fs/file_table.c                   |   1 +
 fs/fuse/file.c                    |   1 +
 fs/gfs2/file.c                    |   1 +
 fs/inode.c                        |   1 +
 fs/ksmbd/smb2pdu.c                |   1 +
 fs/ksmbd/vfs.c                    |   1 +
 fs/ksmbd/vfs_cache.c              |   1 +
 fs/lockd/clntlock.c               |   2 +-
 fs/lockd/clntproc.c               |   3 +-
 fs/lockd/netns.h                  |   1 +
 fs/locks.c                        |  29 ++--
 fs/namei.c                        |   1 +
 fs/nfs/file.c                     |   1 +
 fs/nfs/nfs4_fs.h                  |   1 +
 fs/nfs/pagelist.c                 |   1 +
 fs/nfs/write.c                    |   1 +
 fs/nfs_common/grace.c             |   1 +
 fs/nfsd/netns.h                   |   1 +
 fs/nfsd/nfs4state.c               |   4 +-
 fs/ocfs2/locks.c                  |   1 +
 fs/ocfs2/stack_user.c             |   1 +
 fs/open.c                         |   3 +-
 fs/orangefs/file.c                |   1 +
 fs/posix_acl.c                    |   1 +
 fs/proc/fd.c                      |   1 +
 fs/utimes.c                       |   1 +
 fs/xattr.c                        |   1 +
 fs/xfs/xfs_linux.h                |   1 +
 include/linux/filelock.h          | 439 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/fs.h                | 429 --------------------------------------------------------
 include/linux/lockd/lockd.h       |   4 +-
 include/linux/lockd/xdr.h         |   1 +
 46 files changed, 507 insertions(+), 457 deletions(-)
 create mode 100644 include/linux/filelock.h

-- 
Jeff Layton <jlayton@kernel.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]

             reply	other threads:[~2023-02-16 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 11:07 Jeff Layton [this message]
2023-02-20 20:20 ` 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=c56632e59e4c5b727619de7dd79db11d15bdca6f.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.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

all inboxes | Powered by JetHome®