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 v3 0/9] smb/client: fix mode 0 fallocate handling
Date: Fri, 26 Jun 2026 00:01:45 +0800	[thread overview]
Message-ID: <20260625160154.104450-1-huiwen.he@linux.dev> (raw)

From: Huiwen He <hehuiwen@kylinos.cn>

Changes in v3:

- Move the v2 patch 6 to patch 9, so AllocationSize verification runs after
  the zero-write emulation fixes.
- Extend the v2 patch 9 and move it to patch 8.  It now also handles small
  mode 0 fallocate ranges past EOF, preserving the intervening hole for the
  generic/213 case.
- Update the related commit messages and test notes.

Thanks,
Huiwen He

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

Huiwen He (9):
  smb/client: name the default fallocate mode
  smb/client: preserve errors from smb2_set_sparse()
  smb/client: handle smb2_set_sparse() failure in EOF-extending
    fallocate
  smb/client: handle smb2_set_sparse() failure in non-extending
    fallocate
  smb/client: do not account EOF extension as allocation
  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/inode.c     |  13 ++-
 fs/smb/client/smb2ops.c   | 183 ++++++++++++++++++++++++++++++--------
 fs/smb/client/smb2pdu.c   |  19 ++++
 fs/smb/client/smb2proto.h |   3 +
 fs/smb/common/fscc.h      |   5 ++
 5 files changed, 184 insertions(+), 39 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-06-25 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 16:01 Huiwen He [this message]
2026-06-25 16:01 ` [PATCH v3 1/9] smb/client: name the default fallocate mode Huiwen He
2026-06-25 16:01 ` [PATCH v3 2/9] smb/client: preserve errors from smb2_set_sparse() Huiwen He
2026-06-25 16:01 ` [PATCH v3 3/9] smb/client: handle smb2_set_sparse() failure in EOF-extending fallocate Huiwen He
2026-06-25 16:01 ` [PATCH v3 4/9] smb/client: handle smb2_set_sparse() failure in non-extending fallocate Huiwen He
2026-06-25 16:01 ` [PATCH v3 5/9] smb/client: do not account EOF extension as allocation Huiwen He
2026-06-25 16:01 ` [PATCH v3 6/9] smb/client: handle overlapping allocated ranges in fallocate Huiwen He
2026-06-25 16:01 ` [PATCH v3 7/9] smb/client: reduce fallocate zero buffer allocation Huiwen He
2026-06-25 16:01 ` [PATCH v3 8/9] smb/client: emulate small mode 0 fallocate ranges at or past EOF Huiwen He
2026-06-25 16:01 ` [PATCH v3 9/9] smb/client: verify 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=20260625160154.104450-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.