linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@poochiereds.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Benjamin Coddington <bcodding@redhat.com>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [GIT PULL] please pull file-locking related changes for v4.3
Date: Sun, 1 Nov 2015 21:05:33 -0500	[thread overview]
Message-ID: <20151101210533.268feaf1@synchrony.poochiereds.net> (raw)
In-Reply-To: <CA+55aFznFPUsTVE6UdB-4j3S6q8EdAxYW5Upnw+Z7hs5cTbg9Q@mail.gmail.com>

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

On Sun, 1 Nov 2015 17:45:54 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sun, Nov 1, 2015 at 5:41 PM, Jeff Layton <jlayton@poochiereds.net> wrote:
> >
> > Yes, indeed -- facepalm.
> >
> > Would you like me to push a new tag and send a new pull req?
> 
> It's fine as-is, I just wanted to verify the (fairly obvious) issue,
> that this wasn't something you had actually expected to make 4.3.
> 
> I won't pull it until tomorrow anyway (I want to leave 4.3 alone for a
> day to let people at least get a *chance* of testing it before I start
> acting on the merge window), so if you want to update your tag names
> etc you have time, but it doesn't really matter.
> 
>               Linus

Ok, thanks. I went ahead and fixed the tag. Here's a revised pull req:

The following changes since commit 1f93e4a96c9109378204c147b3eec0d0e8100fde:

  Linux 4.3-rc2 (2015-09-20 14:32:34 -0700)

are available in the git repository at:

  git://git.samba.org/jlayton/linux.git tags/locks-v4.4-1

for you to fetch changes up to 616fb38fa7a9599293e05ae1fa9acfaf73922434:

  locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait (2015-10-22 14:57:42 -0400)

----------------------------------------------------------------
File locking related changes for v4.4 (pile #1)

The largest series of changes is from Ben who offered up a set to add a
new helper function for setting locks based on the type set in fl_flags.
Dmitry also send in a fix for a potential race that he found with KTSAN.
----------------------------------------------------------------
Benjamin Coddington (4):
      locks: Use more file_inode and fix a comment
      locks: introduce locks_lock_inode_wait()
      Move locks API users to locks_lock_inode_wait()
      locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait

Dmitry Vyukov (1):
      fs: fix data races on inode->i_flctx

Jeff Layton (1):
      locks: change tracepoint for generic_add_lease

 drivers/staging/lustre/lustre/llite/file.c |   8 +--
 fs/9p/vfs_file.c                           |   4 +-
 fs/ceph/locks.c                            |   4 +-
 fs/cifs/file.c                             |   2 +-
 fs/dlm/plock.c                             |   4 +-
 fs/fuse/file.c                             |   2 +-
 fs/gfs2/file.c                             |   8 +--
 fs/lockd/clntproc.c                        |  13 +---
 fs/locks.c                                 | 106 ++++++++++++++++++-----------
 fs/nfs/file.c                              |  13 +---
 fs/nfs/nfs4proc.c                          |  13 +---
 fs/ocfs2/locks.c                           |   8 +--
 include/linux/fs.h                         |  21 ++----
 include/trace/events/filelock.h            |  38 ++++++++++-
 14 files changed, 127 insertions(+), 117 deletions(-)

-- 
Jeff Layton <jlayton@poochiereds.net>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-11-02  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  1:21 [GIT PULL] please pull file-locking related changes for v4.3 Jeff Layton
2015-11-02  1:24 ` Linus Torvalds
2015-11-02  1:41   ` Jeff Layton
2015-11-02  1:45     ` Linus Torvalds
2015-11-02  2:05       ` Jeff Layton [this message]

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=20151101210533.268feaf1@synchrony.poochiereds.net \
    --to=jlayton@poochiereds.net \
    --cc=bcodding@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=dvyukov@google.com \
    --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 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).