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 v4 0/7] smb/client: fix fallocate and allocation accounting
Date: Fri, 26 Jun 2026 21:47:12 +0800	[thread overview]
Message-ID: <20260626134719.158270-1-huiwen.he@linux.dev> (raw)

From: Huiwen He <hehuiwen@kylinos.cn>

Changes in v4:

- Add new patch 1 to refresh i_blocks after successful duplicate-extents.
  This fixes stale st_blocks after reflink and avoids the generic/370
  swapon hole-check regression.

The following patches from v2 have already been merged into cifs-2.6.git for-next:
  - smb/client: do not account EOF extension as allocation
  - smb/client: preserve errors from smb2_set_sparse()
  - smb/client: name the default fallocate mode

Link to v3:
https://lore.kernel.org/linux-cifs/20260625160154.104450-1-huiwen.he@linux.dev

Link to v2:
https://lore.kernel.org/linux-cifs/20260624021550.1548952-1-huiwen.he@linux.dev

Thanks,
Huiwen

Huiwen He (7):
  smb/client: refresh allocation size after duplicate extents
  smb/client: handle smb2_set_sparse() failure in EOF-extending
    fallocate
  smb/client: handle smb2_set_sparse() failure in non-extending
    fallocate
  smb/client: handle overlapping allocated ranges in fallocate
  smb/client: reduce fallocate zero buffer allocation
  smb/client: emulate small mode 0 fallocate ranges at or past EOF
  smb/client: verify allocation after EOF-extending fallocate

 fs/smb/client/smb2ops.c   | 169 +++++++++++++++++++++++++++++++++-----
 fs/smb/client/smb2pdu.c   |  19 +++++
 fs/smb/client/smb2proto.h |   3 +
 fs/smb/common/fscc.h      |   5 ++
 4 files changed, 175 insertions(+), 21 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-06-26 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 13:47 Huiwen He [this message]
2026-06-26 13:47 ` [PATCH v4 1/7] smb/client: refresh allocation size after duplicate extents Huiwen He
2026-06-26 13:47 ` [PATCH v4 2/7] smb/client: handle smb2_set_sparse() failure in EOF-extending fallocate Huiwen He
2026-06-26 13:47 ` [PATCH v4 3/7] smb/client: handle smb2_set_sparse() failure in non-extending fallocate Huiwen He
2026-06-26 13:47 ` [PATCH v4 4/7] smb/client: handle overlapping allocated ranges in fallocate Huiwen He
2026-06-26 13:47 ` [PATCH v4 5/7] smb/client: reduce fallocate zero buffer allocation Huiwen He
2026-06-26 13:47 ` [PATCH v4 6/7] smb/client: emulate small mode 0 fallocate ranges at or past EOF Huiwen He
2026-06-27 18:04   ` Steve French
2026-06-26 13:47 ` [PATCH v4 7/7] smb/client: verify allocation after EOF-extending fallocate Huiwen He
2026-06-27 18:06 ` [PATCH v4 0/7] smb/client: fix fallocate and allocation accounting Steve French
2026-06-27 18:13   ` Steve French

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=20260626134719.158270-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.