From: Huiwen He <huiwen.he@linux.dev>
To: smfrench@gmail.com, linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, metze@samba.org, chenxiaosong@kylinos.cn
Cc: linux-cifs@vger.kernel.org
Subject: [PATCH v8 0/5] smb: fix fallocate and allocation accounting
Date: Fri, 3 Jul 2026 13:32:54 +0800 [thread overview]
Message-ID: <20260703053300.913371-1-huiwen.he@linux.dev> (raw)
From: Huiwen He <hehuiwen@kylinos.cn>
Changes in v8:
- Add back the overlapping allocated-range fix as patch 2. This patch
was dropped after v5, but it addresses Shashiko's review comments
about overlapping allocated ranges and malformed range lengths.
Although I could not reproduce this locally, a malicious or unusualserver
could theoretically return such a range.
- Rebase the later patches on top of the restored patch 2. No other
behavior change is intended.
The following patch merged into #ksmbd-for-next-next is not resent:
- smb/server: map SET_INFO ENOSPC to disk full
The following patches are already in upstream and are not resent:
- 898d280f4e4d smb/client: name the default fallocate mode
- 2a4b3d2db5c6 smb/client: preserve errors from smb2_set_sparse()
- 99cd0a6eeb6c smb/client: do not account EOF extension as allocation
Link to v7:
https://lore.kernel.org/linux-cifs/20260702151255.886945-1-huiwen.he@linux.dev
Thanks,
Huiwen
Huiwen He (5):
smb/client: refresh allocation size after duplicate extents
smb/client: handle overlapping allocated ranges in fallocate
smb/client: reduce fallocate zero buffer allocation
smb/client: emulate small EOF-extending mode 0 fallocate ranges
smb/client: refresh allocation after EOF-extending fallocate
fs/smb/client/cifsfs.c | 10 ++-
fs/smb/client/smb2ops.c | 172 +++++++++++++++++++++++++++++++++-----
fs/smb/client/smb2pdu.c | 19 +++++
fs/smb/client/smb2proto.h | 3 +
fs/smb/common/fscc.h | 5 ++
fs/smb/server/smb2pdu.h | 4 -
6 files changed, 185 insertions(+), 28 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-03 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 5:32 Huiwen He [this message]
2026-07-03 5:32 ` [PATCH v8 1/5] smb/client: refresh allocation size after duplicate extents Huiwen He
2026-07-03 5:32 ` [PATCH v8 2/5] smb/client: handle overlapping allocated ranges in fallocate Huiwen He
2026-07-03 5:32 ` [PATCH v8 3/5] smb/client: reduce fallocate zero buffer allocation Huiwen He
2026-07-03 5:32 ` [PATCH v8 4/5] smb/client: emulate small EOF-extending mode 0 fallocate ranges Huiwen He
2026-07-03 5:32 ` [PATCH v8 5/5] smb/client: refresh allocation after EOF-extending fallocate Huiwen He
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=20260703053300.913371-1-huiwen.he@linux.dev \
--to=huiwen.he@linux.dev \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.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