Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: chenxiaosong.chenxiaosong@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, nspmangalore@gmail.com,
	henrique.carvalho@suse.com, meetakshisetiyaoss@gmail.com,
	ematsumiya@suse.de, pali@kernel.org
Cc: linux-cifs@vger.kernel.org, ChenXiaoSong <chenxiaosong@chenxiaosong.com>
Subject: [PATCH v3 0/1] smb/client: fix memory leaks
Date: Mon,  2 Feb 2026 09:49:05 +0000	[thread overview]
Message-ID: <20260202094906.1933479-1-chenxiaosong.chenxiaosong@linux.dev> (raw)

From: ChenXiaoSong <chenxiaosong@chenxiaosong.com>

v2->v3: rebased on mainline

v2: https://lore.kernel.org/linux-cifs/20260202082407.1881618-1-chenxiaosong.chenxiaosong@linux.dev/

The following patches from v2 have already been merged into cifs-2.6.git for-next:
  - smb/client: fix memory leak in smb2_open_file(): https://lore.kernel.org/linux-cifs/20260202082407.1881618-3-chenxiaosong.chenxiaosong@linux.dev/

For detailed information, please see the link: https://chenxiaosong.com/en/smb-buildbot.html (I will ensure this link is always accessible).

ChenXiaoSong (1):
  smb/client: fix memory leak in SendReceive()

 fs/smb/client/cifstransport.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

-- 
2.52.0


             reply	other threads:[~2026-02-02  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  9:49 chenxiaosong.chenxiaosong [this message]
2026-02-02  9:49 ` [PATCH v3 1/1] smb/client: fix memory leak in SendReceive() chenxiaosong.chenxiaosong
2026-02-02 12:17   ` Paulo Alcantara
2026-02-02 15:36   ` David Howells
2026-02-02 16:15     ` 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=20260202094906.1933479-1-chenxiaosong.chenxiaosong@linux.dev \
    --to=chenxiaosong.chenxiaosong@linux.dev \
    --cc=bharathsm@microsoft.com \
    --cc=chenxiaosong@chenxiaosong.com \
    --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