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@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] afs: Fixes
Date: Thu, 18 Apr 2019 10:17:32 +0100	[thread overview]
Message-ID: <26449.1555579052@warthog.procyon.org.uk> (raw)

Hi Linus,

Could you pull these afs fixes please?  There are five:

 (1) Stop using the deprecated get_seconds().

 (2) Don't make tracepoint strings const as the section they go in isn't
     read-only.

 (3) Differentiate failure due to unmarshalling from other failure cases -
     we shouldn't abort with RXGEN_CC/SS_UNMARSHAL if it's not due to
     unmarshalling.

 (4) Add a missing unlock_page().

 (5) Fix the interaction between receiving a notification from a server
     that it has invalidated all outstanding callback promises and a client
     call that we're in the middle of making that will get a new promise.

Tested-by: Jonathan Billings <jsbillin@umich.edu>

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

  ipv4: recompile ip options in ipv4_link_failure (2019-04-12 17:23:46 -0700)

are available in the Git repository at:

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

for you to fetch changes up to eeba1e9cf31d064284dd1fa7bd6cfe01395bd03d:

  afs: Fix in-progess ops to ignore server-level callback invalidation (2019-04-13 08:37:37 +0100)

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

----------------------------------------------------------------
Andi Kleen (1):
      afs: Avoid section confusion in CM_NAME

Arnd Bergmann (1):
      afs: avoid deprecated get_seconds()

David Howells (2):
      afs: Differentiate abort due to unmarshalling from other errors
      afs: Fix in-progess ops to ignore server-level callback invalidation

Marc Dionne (1):
      afs: Unlock pages for __pagevec_release()

 fs/afs/callback.c  | 3 +--
 fs/afs/cmservice.c | 2 +-
 fs/afs/inode.c     | 4 +---
 fs/afs/internal.h  | 4 +---
 fs/afs/rxrpc.c     | 6 +++++-
 fs/afs/server.c    | 1 -
 fs/afs/write.c     | 1 +
 7 files changed, 10 insertions(+), 11 deletions(-)

             reply	other threads:[~2019-04-18  9:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  9:17 David Howells [this message]
2019-04-18 15:20 ` pr-tracker-bot
  -- 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
2018-05-14 21:25 [GIT PULL] afs: Fixes David Howells
2017-11-24 14:22 David Howells
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
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=26449.1555579052@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.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