From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, iwienand@redhat.com,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [GIT PULL] AFS fixes
Date: Wed, 26 Jun 2019 14:39:53 +0100 [thread overview]
Message-ID: <11571.1561556393@warthog.procyon.org.uk> (raw)
Hi Linus,
Could you pull this please?
There are four patches:
(1) Fix the printing of the "vnode modified" warning to exclude checks on
files for which we don't have a callback promise from the server (and
so don't expect the server to tell us when it changes).
Without this, for every file or directory for which we still have an
in-core inode that gets changed on the server, we may get a message
logged when we next look at it. This can happen in bulk if, for
instance, someone does "vos release" to update a R/O volume from a R/W
volume and a whole set of files are all changed together.
We only really want to log a message if the file changed and the
server didn't tell us about it or we failed to track the state
internally.
(2) Fix accidental corruption of either afs_vlserver struct objects or the
the following memory locations (which could hold anything). The issue
is caused by a union that points to two different structs in struct
afs_call (to save space in the struct). The call cleanup code assumes
that it can simply call the cleanup for one of those structs if not
NULL - when it might be actually pointing to the other struct.
This means that every Volume Location RPC op is going to corrupt
something.
(3) Fix an uninitialised spinlock. This isn't too bad, it just causes a
one-off warning if lockdep is enabled when "vos release" is called,
but the spinlock still behaves correctly.
(4) Fix the setting of i_block in the inode. This causes du, for example,
to produce incorrect results, but otherwise should not be dangerous to
the kernel.
The in-kernel AFS client has been undergoing testing on opendev.org on one
of their mirror machines. They are using AFS to hold data that is then
served via apache, and Ian Wienand had reported seeing oopses, spontaneous
machine reboots and updates to volumes going missing. This patch series
appears to have fixed the problem, very probably due to patch (2), but it's
not 100% certain.
Reviewed-by: Jeffrey Altman <jaltman@auristor.com>
Tested-by: Marc Dionne <marc.dionne@auristor.com>
Tested-by: Ian Wienand <iwienand@redhat.com>
---
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/afs-fixes-20190620
for you to fetch changes up to 2cd42d19cffa0ec3dfb57b1b3e1a07a9bf4ed80a:
afs: Fix setting of i_blocks (2019-06-20 18:12:02 +0100)
----------------------------------------------------------------
AFS fixes
----------------------------------------------------------------
David Howells (4):
afs: Fix over zealous "vnode modified" warnings
afs: Fix vlserver record corruption
afs: Fix uninitialised spinlock afs_volume::cb_break_lock
afs: Fix setting of i_blocks
fs/afs/callback.c | 4 ++--
fs/afs/inode.c | 31 +++++++++++++++++++------------
fs/afs/internal.h | 8 +++-----
fs/afs/volume.c | 1 +
4 files changed, 25 insertions(+), 19 deletions(-)
next reply other threads:[~2019-06-26 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:39 David Howells [this message]
2019-06-28 0:45 ` [GIT PULL] AFS fixes 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-14 14:18 David Howells
2019-08-14 22:35 ` pr-tracker-bot
2019-08-14 14:15 David Howells
2019-06-26 8:50 [GIT PULL] AFS fixes 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=11571.1561556393@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=iwienand@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).