linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Marc Dionne <marc.dionne@auristor.com>,
	dhowells@redhat.com, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] AFS fixes
Date: Thu, 17 Jan 2019 15:27:29 +0000	[thread overview]
Message-ID: <154773884927.24105.2730570814701376379.stgit@warthog.procyon.org.uk> (raw)


Hi Linus,

Here's a set of fixes for AFS:

 (1) Use struct_size() for kzalloc() size calculation.

 (2) When calling YFS.CreateFile rather than AFS.CreateFile, it is possible
     to create a file with a file lock already held.  The default value
     indicating no lock required is actually -1, not 0.

 (3) Fix an oops in inode/vnode validation if the target inode doesn't have
     a server interest assigned (ie. a server that will notify us of
     changes by third parties).

 (4) Fix refcounting of keys in file locking.

 (5) Fix a race in refcounting asynchronous operations in the event of an
     error during request transmission.  The provision of a dedicated
     function to get an extra ref on a call is split into a separate
     commit.

The patches can be found here:

	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git
	tag afs-fixes-20190117

David
---
David Howells (3):
      afs: Fix key refcounting in file locking code
      afs: Provide a function to get a ref on a call
      afs: Fix race in async call refcounting

Gustavo A. R. Silva (1):
      afs: Use struct_size() in kzalloc()

Marc Dionne (2):
      afs: Set correct lock type for the yfs CreateFile
      afs: Don't set vnode->cb_s_break in afs_validate()


 fs/afs/flock.c             |    4 ++-
 fs/afs/inode.c             |    3 ++
 fs/afs/protocol_yfs.h      |   11 +++++++++
 fs/afs/rxrpc.c             |   53 +++++++++++++++++++++++++++++++++++---------
 fs/afs/server_list.c       |    4 +--
 fs/afs/yfsclient.c         |    2 +-
 include/trace/events/afs.h |    2 ++
 7 files changed, 61 insertions(+), 18 deletions(-)


             reply	other threads:[~2019-01-17 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 15:27 David Howells [this message]
2019-01-17 15:27 ` [PATCH 1/6] afs: Use struct_size() in kzalloc() David Howells
2019-01-17 15:27 ` [PATCH 2/6] afs: Set correct lock type for the yfs CreateFile David Howells
2019-01-17 15:27 ` [PATCH 3/6] afs: Don't set vnode->cb_s_break in afs_validate() David Howells
2019-01-17 15:27 ` [PATCH 4/6] afs: Fix key refcounting in file locking code David Howells
2019-01-17 15:28 ` [PATCH 5/6] afs: Provide a function to get a ref on a call David Howells
2019-01-17 15:28 ` [PATCH 6/6] afs: Fix race in async call refcounting David Howells
2019-01-17 18:29 ` [PATCH 0/6] AFS fixes Linus Torvalds
2019-01-17 18:31   ` Linus Torvalds
2020-06-09 16:13 [PATCH 0/6] afs: Fixes David Howells

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=154773884927.24105.2730570814701376379.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=gustavo@embeddedor.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --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).