From: ChenXiaoSong <chenxiaosong2@huawei.com>
To: Zhang Xiaoxu <zhangxiaoxu5@huawei.com>,
<linux-cifs@vger.kernel.org>, <sfrench@samba.org>,
<smfrench@gmail.com>, <pc@cjr.nz>
Cc: <lsahlber@redhat.com>, <sprasad@microsoft.com>, <tom@talpey.com>
Subject: Re: [PATCH v2 0/2] Fix some bug in cifs
Date: Fri, 3 Mar 2023 10:02:52 +0800 [thread overview]
Message-ID: <c6a6e4a0-a66b-e86c-8c67-fdd24fbfcce2@huawei.com> (raw)
In-Reply-To: <20221116031136.3967579-1-zhangxiaoxu5@huawei.com>
Hi Steve and Paulo:
Do you have any suggestions for this patchset ?
xfstests generic/011 always report this bug, our mount option is: -o
mfsymlinks,vers=3.0
在 2022/11/16 11:11, Zhang Xiaoxu 写道:
> v2:
> - remove the 1st patch since steve already merged it into repo.
> - fix cifs 1.0 hung since not set READY flag when wakeup task
> on 2nd patch.
>
> Zhang Xiaoxu (2):
> cifs: Fix UAF in cifs_demultiplex_thread()
> cifs: Move the in_send statistic to __smb_send_rqst()
>
> fs/cifs/cifsglob.h | 1 +
> fs/cifs/transport.c | 55 ++++++++++++++++++++++++++-------------------
> 2 files changed, 33 insertions(+), 23 deletions(-)
>
next prev parent reply other threads:[~2023-03-03 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 3:11 [PATCH v2 0/2] Fix some bug in cifs Zhang Xiaoxu
2022-11-16 3:11 ` [PATCH v2 1/2] cifs: Fix UAF in cifs_demultiplex_thread() Zhang Xiaoxu
2022-11-16 3:11 ` [PATCH v2 2/2] cifs: Move the in_send statistic to __smb_send_rqst() Zhang Xiaoxu
2023-09-01 15:25 ` Paulo Alcantara
2023-09-01 16:25 ` Steve French
2023-09-01 16:49 ` Paulo Alcantara
2023-03-03 2:02 ` ChenXiaoSong [this message]
2023-03-03 21:55 ` [PATCH v2 0/2] Fix some bug in cifs Paulo Alcantara
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=c6a6e4a0-a66b-e86c-8c67-fdd24fbfcce2@huawei.com \
--to=chenxiaosong2@huawei.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=pc@cjr.nz \
--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;
as well as URLs for NNTP newsgroup(s).