From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian@brauner.io>
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: Miscellaneous fixes
Date: Thu, 23 Jul 2026 12:34:45 +0100 [thread overview]
Message-ID: <20260723113452.566619-1-dhowells@redhat.com> (raw)
Hi Christian,
Can you pick up these miscellaneous AFS fixes, please? Note that most of
these are derived from Sashiko review of some rxrpc patches[1][2].
(1) Fix afs_fs_fetch_data() to set call->async.
(2) Fix afs_fs_fetch_data() to subtract transferred from len instead of
adding it.
(3) Fix a UAF when sending a message if the call is completed so quickly
that the sending code hasn't finished with it when it gets freed.
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
[1] https://sashiko.dev/#/patchset/20260702144919.172295-1-dhowells%40redh
[2] https://sashiko.dev/#/patchset/20260713081022.2186481-1-dhowells%40red
David Howells (3):
afs: Fix afs_fs_fetch_data() to set call->async
afs: Fix afs_fs_fetch_data() to subtract transferred from len
afs: Fix UAF when sending a message
fs/afs/fsclient.c | 5 ++++-
fs/afs/internal.h | 3 ++-
2 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2026-07-23 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:34 David Howells [this message]
2026-07-23 11:34 ` [PATCH 1/3] afs: Fix afs_fs_fetch_data() to set call->async David Howells
2026-07-23 11:34 ` [PATCH 2/3] afs: Fix afs_fs_fetch_data() to subtract transferred from len David Howells
2026-07-23 11:34 ` [PATCH 3/3] afs: Fix UAF when sending a message David Howells
2026-07-28 7:21 ` [PATCH 0/3] afs: Miscellaneous fixes Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2021-07-12 12:57 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=20260723113452.566619-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=christian@brauner.io \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
/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
all inboxes | Powered by JetHome®