From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: Steve French <smfrench@gmail.com>
Cc: linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, nspmangalore@gmail.com,
henrique.carvalho@suse.com, meetakshisetiyaoss@gmail.com,
ematsumiya@suse.de, pali@kernel.org, linux-cifs@vger.kernel.org,
ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: Re: [PATCH v2 1/2] smb/client: fix memory leak in SendReceive()
Date: Mon, 2 Feb 2026 17:11:24 +0800 [thread overview]
Message-ID: <7662c0de-b654-46c4-b3ca-aab3e4139574@linux.dev> (raw)
In-Reply-To: <CAH2r5mt3nUrW_qvWCCHkiBPCoXg0XdwV07_wS+7Ls3p7AQ81HA@mail.gmail.com>
Should I send new version rebased on mainline? In that case, some of
David's patches for the next merge window need further changes.
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 2/2/26 4:50 PM, Steve French wrote:
> merged both into cifs-2.6.git for-next but this smb1 patch has
> dependencies on other patches for next merge window so might have been
> better to rebase on mainline so we could send sooner (although that
> would also require changing at least one other patch in for-next).
next prev parent reply other threads:[~2026-02-02 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 8:24 [PATCH v2 0/2] smb/client: fix memory leaks chenxiaosong.chenxiaosong
2026-02-02 8:24 ` [PATCH v2 1/2] smb/client: fix memory leak in SendReceive() chenxiaosong.chenxiaosong
2026-02-02 8:50 ` Steve French
2026-02-02 9:11 ` ChenXiaoSong [this message]
2026-02-02 8:24 ` [PATCH v2 2/2] smb/client: fix memory leak in smb2_open_file() chenxiaosong.chenxiaosong
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=7662c0de-b654-46c4-b3ca-aab3e4139574@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=ematsumiya@suse.de \
--cc=henrique.carvalho@suse.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=meetakshisetiyaoss@gmail.com \
--cc=nspmangalore@gmail.com \
--cc=pali@kernel.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