Linux filesystem development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian@brauner.io>
Cc: David Howells <dhowells@redhat.com>,
	Paulo Alcantara <pc@manguebit.org>,
	netfs@lists.linux.dev, linux-afs@lists.infradead.org,
	linux-cifs@vger.kernel.org, ceph-devel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] netfs, cachefiles: Miscellaneous fixes
Date: Mon, 24 Aug 2026 13:02:19 +0100	[thread overview]
Message-ID: <20260824120224.504575-1-dhowells@redhat.com> (raw)

Hi Christian,

Here are a couple of miscellaneous fixes for netfslib and one for cachefiles,
if you could pick them up?

 (1) Fix an uninitialised return value from netfs_unbuffered_write().

 (2) Fix read progress reporting to avoid 64-bit tearing on a 32-bit
     machine.  This has been modified from the previous submission as part
     of a different series to take account of a sashiko reported issue[1].

 (3) Fix a potential UAF/KASAN warning reported by sashiko[1] in cachefiles in
     which the coherency data buffer is cast to a __be64* and dereferenced in
     a tracepoint - even though it might not be at least that large (or
     aligned).

The patches can also be found here:

	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-fixes

Thanks,
David

[1] https://sashiko.dev/#/patchset/20260810144746.574036-1-dhowells%40redhat.com

David Howells (2):
  netfs: Fix read progress reporting
  cachefiles: Fix potential UAF/KASAN warning

Karl Mehltretter (1):
  netfs: Fix uninitialized return value in netfs_unbuffered_write()

 fs/cachefiles/xattr.c             | 16 ++++-----
 fs/netfs/buffered_read.c          |  4 +++
 fs/netfs/direct_write.c           |  2 +-
 fs/netfs/internal.h               |  1 +
 fs/netfs/objects.c                | 32 ++++++++++-------
 fs/netfs/read_collect.c           | 58 +++++++++++++++++++++++--------
 fs/netfs/read_single.c            |  2 ++
 include/linux/netfs.h             |  2 +-
 include/trace/events/cachefiles.h | 19 ++++++++--
 include/trace/events/netfs.h      | 21 +++++++++++
 10 files changed, 119 insertions(+), 38 deletions(-)


             reply	other threads:[~2026-08-24 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 12:02 David Howells [this message]
2026-08-24 12:02 ` [PATCH 1/3] netfs: Fix uninitialized return value in netfs_unbuffered_write() David Howells
2026-08-24 12:02 ` [PATCH 2/3] netfs: Fix read progress reporting David Howells
2026-08-24 12:02 ` [PATCH 3/3] cachefiles: Fix potential UAF/KASAN warning 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=20260824120224.504575-1-dhowells@redhat.com \
    --to=dhowells@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=christian@brauner.io \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=pc@manguebit.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