From: Paulo Alcantara <pc@cjr.nz>
To: Zhang Xiaoxu <zhangxiaoxu5@huawei.com>,
linux-cifs@vger.kernel.org, zhangxiaoxu5@huawei.com,
sfrench@samba.org, smfrench@gmail.com, lsahlber@redhat.com,
sprasad@microsoft.com, tom@talpey.com, aaptel@suse.com
Subject: Re: [PATCH 0/5] cifs: Fix xid leak in cifs
Date: Mon, 17 Oct 2022 10:53:39 -0300 [thread overview]
Message-ID: <87o7uad09o.fsf@cjr.nz> (raw)
In-Reply-To: <20221017144525.414313-1-zhangxiaoxu5@huawei.com>
Zhang Xiaoxu <zhangxiaoxu5@huawei.com> writes:
> Zhang Xiaoxu (5):
> cifs: Fix xid leak in cifs_create()
> cifs: Fix xid leak in cifs_copy_file_range()
> cifs: Fix xid leak in cifs_flock()
> cifs: Fix xid leak in cifs_ses_add_channel()
> cifs: Fix xid leak in cifs_get_file_info_unix()
>
> fs/cifs/cifsfs.c | 7 +++++--
> fs/cifs/dir.c | 6 ++++--
> fs/cifs/file.c | 11 +++++++----
> fs/cifs/inode.c | 6 ++++--
> fs/cifs/sess.c | 1 +
> 5 files changed, 21 insertions(+), 10 deletions(-)
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
next prev parent reply other threads:[~2022-10-17 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 14:45 [PATCH 0/5] cifs: Fix xid leak in cifs Zhang Xiaoxu
2022-10-17 13:53 ` Paulo Alcantara [this message]
2022-10-17 14:45 ` [PATCH 1/5] cifs: Fix xid leak in cifs_create() Zhang Xiaoxu
2022-10-17 14:45 ` [PATCH 2/5] cifs: Fix xid leak in cifs_copy_file_range() Zhang Xiaoxu
2022-10-17 14:45 ` [PATCH 3/5] cifs: Fix xid leak in cifs_flock() Zhang Xiaoxu
2022-10-17 14:45 ` [PATCH 4/5] cifs: Fix xid leak in cifs_ses_add_channel() Zhang Xiaoxu
2022-10-17 17:28 ` Steve French
2022-10-17 14:45 ` [PATCH 5/5] cifs: Fix xid leak in cifs_get_file_info_unix() Zhang Xiaoxu
2022-10-17 17:28 ` [PATCH 0/5] cifs: Fix xid leak in cifs 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=87o7uad09o.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=zhangxiaoxu5@huawei.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