From: Valerie Aurora <val@versity.com>
To: rpdfs-devel@lists.linux.dev
Subject: [PATCH 0/6] File data read/write version 2
Date: Thu, 7 May 2026 15:21:47 +0200 [thread overview]
Message-ID: <20260507132153.1161324-1-val@versity.com> (raw)
This patch set implements file data read/write with most of the
previous code review comments resolved. The main exception is that
->writepages() is not yet implemented.
Valerie Aurora (6):
rpdfs: add rpdfs_file_llseek
rpdfs: add inode change debugging routine
rpdfs: add basic file data initialization
rpdfs: add file data allocation and lookup routines
rpdfs: add rpdfs_write_iter/rpdfs_read_iter
rpdfs: add read_folio, dirty_folio, write_begin, write_end
fs/rpdfs/Makefile | 1 +
fs/rpdfs/data.c | 598 ++++++++++++++++++++++++++++++++++++++++
fs/rpdfs/data.h | 11 +
fs/rpdfs/file.c | 77 ++++++
fs/rpdfs/format-block.h | 32 +--
fs/rpdfs/format-msg.h | 4 +
fs/rpdfs/inode.c | 51 +++-
fs/rpdfs/inode.h | 1 +
8 files changed, 753 insertions(+), 22 deletions(-)
create mode 100644 fs/rpdfs/data.c
create mode 100644 fs/rpdfs/data.h
--
2.49.0
next reply other threads:[~2026-05-07 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 13:21 Valerie Aurora [this message]
2026-05-07 13:21 ` [PATCH 1/6] rpdfs: add rpdfs_file_llseek Valerie Aurora
2026-05-07 13:21 ` [PATCH 2/6] rpdfs: add inode change debugging routine Valerie Aurora
2026-05-07 13:21 ` [PATCH 3/6] rpdfs: add basic file data initialization Valerie Aurora
2026-05-07 13:21 ` [PATCH 4/6] rpdfs: add file data allocation and lookup routines Valerie Aurora
2026-05-07 13:21 ` [PATCH 5/6] rpdfs: add rpdfs_write_iter/rpdfs_read_iter Valerie Aurora
2026-05-07 13:21 ` [PATCH 6/6] rpdfs: add read_folio, dirty_folio, write_begin, write_end Valerie Aurora
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=20260507132153.1161324-1-val@versity.com \
--to=val@versity.com \
--cc=rpdfs-devel@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.