From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: "Steve French" <smfrench@gmail.com>,
"Shyam Prasad N" <nspmangalore@gmail.com>,
"David Howells" <dhowells@redhat.com>,
"Henrique Carvalho" <henrique.carvalho@suse.com>,
"Bharath S M" <bharathsm@microsoft.com>,
"Meetakshi Setiya" <meetakshisetiyaoss@gmail.com>,
ChenXiaoSong <chenxiaosong@kylinos.cn>,
"Paulo Alcantara" <pc@manguebit.org>,
"Steve French" <sfrench@samba.org>,
"Enzo Matsumiya" <ematsumiya@suse.de>,
"Pali Rohár" <pali@kernel.org>,
linkinjeon@kernel.org, ChenXiaoSong <chenxiaosong@kylinos.cn>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: xfstests failed test cases
Date: Mon, 2 Feb 2026 14:56:56 +0800 [thread overview]
Message-ID: <efe55da5-67cb-47f2-94d8-76fbe9023c99@linux.dev> (raw)
In-Reply-To: <d6a9cf34-e4ec-4792-afb0-5d7a39b46378@linux.dev>
I have submitted another patch to fix the SMB1 kmemleak issue:
https://lore.kernel.org/linux-cifs/20260202064928.1879323-1-chenxiaosong.chenxiaosong@linux.dev/
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 2/1/26 4:14 PM, ChenXiaoSong wrote:
> I have already submitted a patch to fix this issue: https://
> lore.kernel.org/linux-cifs/20260201081017.998628-1-
> chenxiaosong.chenxiaosong@linux.dev/
>
> Thanks,
> ChenXiaoSong <chenxiaosong@kylinos.cn>
>
> On 2/1/26 2:30 PM, ChenXiaoSong wrote:
>> Steve and I have completed a git bisect and found the first bad commit:
>> [e255612b5ed9f179abe8196df7c2ba09dd227900] cifs: Add fallback for SMB2
>> CREATE without FILE_READ_ATTRIBUTES
>>
>> For detailed information, please check the link: https://
>> chenxiaosong.com/en/smb-buildbot.html#cifs-103-bisect
>>
>> Thanks,
>> ChenXiaoSong <chenxiaosong@kylinos.cn>
>>
>> On 1/29/26 8:20 PM, ChenXiaoSong wrote:
>>> I found the key factor that triggers kmemleak in cifs/103, the
>>> directory exported by the server must be read-only.
>>>
>>> When sharing a folder on Windows, do not check "Allow Change", set
>>> the permissions of the shared directory to read-only.
>>>
>>> Alternatively, `smb.conf` of Samba is configured as follows:
>>> ```
>>> [test]
>>> ...
>>> read only = yes
>>> [test2]
>>> ...
>>> read only = yes
>>> ```
>>>
>>> For detailed information, please check the link: https://
>>> chenxiaosong.com/en/smb-buildbot.html#cifs-103
>>>
>>> I will first try to analyze the code, and if that doesn't work, I
>>> will try to bisect it.
>>>
>>> Thanks,
>>> ChenXiaoSong <chenxiaosong@kylinos.cn>
>>>
>>> On 1/28/26 23:29, ChenXiaoSong wrote:
>>>> I have reproduced the failures of these test cases. For detailed
>>>> information, please check the link: https://chenxiaosong.com/en/smb-
>>>> buildbot.html (I will ensure this link is always accessible).
>>>>
>>>> Perhaps sending these issues to the mailing list could help resolve
>>>> them more quickly.
>>
>
prev parent reply other threads:[~2026-02-02 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH2r5mv41nFwJQwszD82MQbtDV75zVy6=tbwqxDTOsw2hwfBpw@mail.gmail.com>
[not found] ` <CANT5p=qmo_KORMQbnjonapAaGHq=UvWAMzR0jNKBBvx3UUkyjQ@mail.gmail.com>
[not found] ` <CANT5p=pfQE2A++j6W4sEudrSLH6ct=ho4i=k2ZDEecUAX0cReg@mail.gmail.com>
[not found] ` <CAH2r5mvakK7=1i-fZTE9hLLYd_Q3o5z557vQZ5QQtdOTkZeSew@mail.gmail.com>
[not found] ` <CAH2r5mufJgC85ULoVzYSMXDq4=-RUiJ2YgppM434vz1Q4B1d+A@mail.gmail.com>
[not found] ` <CAH2r5msVifsc-E0TjaYXt2Afh1MiCsJTSwMnsDAdUShRgkJ_4A@mail.gmail.com>
[not found] ` <CAH2r5mukVmnfK7X3jXWwRnD-_RAMuUgzXpi+HzNjxOat4tobJA@mail.gmail.com>
[not found] ` <CAH2r5mvW23-eUsjDQ_0oLrmj406Og5sDs-yPgqh6jPwdSEG+Tg@mail.gmail.com>
[not found] ` <CAH2r5mu909vLwAQcKFQX7cWz421V1QmSiBAKyJeC8gUcGVb0Ew@mail.gmail.com>
2026-01-28 15:29 ` xfstests failed test cases ChenXiaoSong
[not found] ` <CAH2r5muyYgm4-Nwvd=d+Sqq7mmd+HGPoyM1tid6dsnN1=vt3Ng@mail.gmail.com>
2026-01-28 15:41 ` ChenXiaoSong
2026-01-29 12:20 ` ChenXiaoSong
2026-02-01 6:30 ` ChenXiaoSong
2026-02-01 8:14 ` ChenXiaoSong
2026-02-02 6:56 ` ChenXiaoSong [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=efe55da5-67cb-47f2-94d8-76fbe9023c99@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=sfrench@samba.org \
--cc=smfrench@gmail.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