From: Paulo Alcantara <pc@manguebit.org>
To: Huiwen He <huiwen.he@linux.dev>,
linkinjeon@kernel.org, ronniesahlberg@gmail.com,
sprasad@microsoft.com, tom@talpey.com, bharathsm@microsoft.com,
senozhatsky@chromium.org, dhowells@redhat.com,
chenxiaosong@kylinos.cn
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH v4 0/7] smb/client: fix fallocate range operation issues
Date: Sun, 30 Aug 2026 17:56:38 -0300 [thread overview]
Message-ID: <3295d5af704d274d37b08d8e59fb7449@manguebit.org> (raw)
In-Reply-To: <20260828071935.552165-1-huiwen.he@linux.dev>
Huiwen He <huiwen.he@linux.dev> writes:
> From: Huiwen He <hehuiwen@kylinos.cn>
>
> This series fixes several issues in SMB3 fallocate range operations,
> including insert range, collapse range, zero range, and punch hole.
> ...
Applied.
prev parent reply other threads:[~2026-08-30 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 7:19 [PATCH v4 0/7] smb/client: fix fallocate range operation issues Huiwen He
2026-08-28 7:19 ` [PATCH v4 1/7] smb/client: validate new EOF for insert range Huiwen He
2026-08-28 7:19 ` [PATCH v4 2/7] smb/client: validate new EOF for zero range Huiwen He
2026-08-28 7:19 ` [PATCH v4 3/7] smb/client: mark file sparse before emulating insert range Huiwen He
2026-08-28 7:19 ` [PATCH v4 4/7] smb/client: fix data corruption in emulated " Huiwen He
2026-08-28 7:19 ` [PATCH v4 5/7] smb/client: fix integer truncation in collapse range Huiwen He
2026-08-28 7:19 ` [PATCH v4 6/7] smb/client: fix stale page cache in insert/collapse range Huiwen He
2026-08-28 7:19 ` [PATCH v4 7/7] smb/client: invalidate fscache for fallocate range operations Huiwen He
2026-08-30 20:56 ` Paulo Alcantara [this message]
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=3295d5af704d274d37b08d8e59fb7449@manguebit.org \
--to=pc@manguebit.org \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=huiwen.he@linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--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.