public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
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>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: xfstests failed test cases
Date: Thu, 29 Jan 2026 20:20:23 +0800	[thread overview]
Message-ID: <f1b9cd58-8a61-4fa7-a7e9-198c2c468c59@linux.dev> (raw)
In-Reply-To: <bcd3d847-c38f-4c88-af07-3da09dad476b@linux.dev>

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.


  parent reply	other threads:[~2026-01-29 12:21 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 [this message]
2026-02-01  6:30                     ` ChenXiaoSong
2026-02-01  8:14                       ` ChenXiaoSong
2026-02-02  6:56                         ` 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=f1b9cd58-8a61-4fa7-a7e9-198c2c468c59@linux.dev \
    --to=chenxiaosong.chenxiaosong@linux.dev \
    --cc=bharathsm@microsoft.com \
    --cc=chenxiaosong@kylinos.cn \
    --cc=dhowells@redhat.com \
    --cc=henrique.carvalho@suse.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=meetakshisetiyaoss@gmail.com \
    --cc=nspmangalore@gmail.com \
    --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