All of lore.kernel.org
 help / color / mirror / Atom feed
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 v7 0/4] smb: fix fallocate and allocation accounting
Date: Thu,  2 Jul 2026 23:12:51 +0800	[thread overview]
Message-ID: <20260702151255.886945-1-huiwen.he@linux.dev> (raw)

From: Huiwen He <hehuiwen@kylinos.cn>

Changes in v7:

- Rework Patch 1 to keeps the duplicate-extents QueryInfo result valid in
  the inode cache, avoiding duplicate revalidation when userspace stats
  the cloned file.

- Rework Patch 3 to no longer uses FSCTL_QUERY_ALLOCATED_RANGES for small
  fallocate ranges that start at or beyond EOF. These ranges are now
  zero-written directly because there are no old allocated ranges to
  preserve there.

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 v6:
https://lore.kernel.org/linux-cifs/20260701152157.822207-1-huiwen.he@linux.dev/

Thanks,
Huiwen

Huiwen He (4):
  smb/client: refresh allocation size after duplicate extents
  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   | 147 ++++++++++++++++++++++++++++++++++----
 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, 167 insertions(+), 21 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-07-02 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 15:12 Huiwen He [this message]
2026-07-02 15:12 ` [PATCH v7 1/4] smb/client: refresh allocation size after duplicate extents Huiwen He
2026-07-02 15:12 ` [PATCH v7 2/4] smb/client: reduce fallocate zero buffer allocation Huiwen He
2026-07-02 15:12 ` [PATCH v7 3/4] smb/client: emulate small EOF-extending mode 0 fallocate ranges Huiwen He
2026-07-02 15:12 ` [PATCH v7 4/4] 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=20260702151255.886945-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 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.