mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, linux-afs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] afs: Fixes
Date: Fri, 24 Nov 2017 14:22:04 +0000	[thread overview]
Message-ID: <26247.1511533324@warthog.procyon.org.uk> (raw)

Hi Linus,

Can you pull these fixes for the AFS filesystem?  They include:

 (1) Make AFS file locking work again.

 (2) Don't write to a page that's being written out, but wait for it to
     complete.

 (3) Do d_drop() and d_add() in the right places.

 (4) Put keys on error paths.

 (5) Remove some redundant code.

Thanks,
David
---
The following changes since commit cf9b0772f2e410645fece13b749bd56505b998b8:

  Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2017-11-16 16:05:01 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/afs-fixes-20171124

for you to fetch changes up to 43dd388b21c722616413781bd434522376e117cc:

  afs: remove redundant assignment of dvnode to itself (2017-11-24 13:55:46 +0000)

----------------------------------------------------------------
AFS fixes

----------------------------------------------------------------
Colin Ian King (1):
      afs: remove redundant assignment of dvnode to itself

David Howells (4):
      afs: Fix file locking
      afs: Make afs_write_begin() avoid writing to a page that's being stored
      afs: Fix some dentry handling in dir ops and missing key_puts
      afs: Fix signal handling in some file ops

Gustavo A. R. Silva (1):
      afs: cell: Remove unnecessary code in afs_lookup_cell

 fs/afs/cell.c        |   7 +-
 fs/afs/dir.c         |  25 +--
 fs/afs/flock.c       | 548 +++++++++++++++++++++++++++++----------------------
 fs/afs/internal.h    |  23 ++-
 fs/afs/rotate.c      |  70 +++++--
 fs/afs/security.c    |   4 +-
 fs/afs/server_list.c |   2 +-
 fs/afs/write.c       |   5 +
 8 files changed, 405 insertions(+), 279 deletions(-)

             reply	other threads:[~2017-11-24 14:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 14:22 David Howells [this message]
2017-11-25 18:05 ` Linus Torvalds
2017-11-25 22:35 ` David Howells
2017-11-25 22:48   ` Dave Chinner
2017-11-25 22:55   ` Linus Torvalds
2017-11-25 23:19   ` David Howells
  -- strict thread matches above, loose matches on Subject: below --
2020-10-29 14:07 [GIT PULL] afs fixes David Howells
2020-10-29 17:31 ` pr-tracker-bot
2020-04-13 14:50 [GIT PULL] afs: Fixes David Howells
2020-04-13 15:13 ` David Howells
2020-04-14 19:05 ` pr-tracker-bot
2019-08-22 13:10 David Howells
2019-08-22 18:30 ` pr-tracker-bot
2019-08-14 14:18 David Howells
2019-08-14 22:35 ` pr-tracker-bot
2019-08-14 14:15 David Howells
2019-06-26 13:39 [GIT PULL] AFS fixes David Howells
2019-06-28  0:45 ` pr-tracker-bot
2019-06-26  8:50 David Howells
2019-06-26 13:38 ` David Howells
2019-04-18  9:17 [GIT PULL] afs: Fixes David Howells
2019-04-18 15:20 ` pr-tracker-bot
2018-05-14 21:25 David Howells
2017-03-17 15:29 [GIT PULL] AFS fixes David Howells
2017-03-17 19:23 ` Linus Torvalds

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=26247.1511533324@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-afs@vger.kernel.org \
    --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

Powered by JetHome