From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] afs: Fix directory size handling
Date: Tue, 2 May 2023 17:35:25 +0100 [thread overview]
Message-ID: <20230502163528.1564398-1-dhowells@redhat.com> (raw)
Hi Linus,
Could you apply these three fixes to AFS directory handling?
(1) Make sure that afs_read_dir() sees any increase in file size if the
file unexpectedly changed on the server (e.g. due to another client
making a change).
(2) Make afs_getattr() always return the server's dir file size, not the
locally edited one, so that pagecache eviction doesn't cause the dir
file size to change unexpectedly.
(3) Prevent afs_read_dir() from getting into an endless loop if the server
indicates that the directory file size is larger than expected.
The patches can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs-fixes
Thanks,
David
---
%(shortlog)s
%(diffstat)s
David Howells (1):
afs: Fix getattr to report server i_size on dirs, not local size
Marc Dionne (2):
afs: Fix updating of i_size with dv jump from server
afs: Avoid endless loop if file is larger than expected
fs/afs/dir.c | 4 ++++
fs/afs/inode.c | 10 +++++++++-
2 files changed, 13 insertions(+), 1 deletion(-)
next reply other threads:[~2023-05-02 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 16:35 David Howells [this message]
2023-05-02 16:35 ` [PATCH 1/3] afs: Fix updating of i_size with dv jump from server David Howells
2023-05-02 16:35 ` [PATCH 2/3] afs: Fix getattr to report server i_size on dirs, not local size David Howells
2023-05-02 16:35 ` [PATCH 3/3] afs: Avoid endless loop if file is larger than expected David Howells
2023-05-02 17:56 ` [PATCH 0/3] afs: Fix directory size handling 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=20230502163528.1564398-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.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).