linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "frank.li@vivo.com" <frank.li@vivo.com>,
	"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"brauner@kernel.org" <brauner@kernel.org>,
	"slava@dubeyko.com" <slava@dubeyko.com>
Subject: Re:  回复: HFS/HFS+ maintainership action items
Date: Fri, 25 Apr 2025 18:02:20 +0000	[thread overview]
Message-ID: <a5560fe32b5869a029891599f2e2d4b9e3d02a6d.camel@ibm.com> (raw)
In-Reply-To: <TYZPR06MB527574C2A8265BF6912994E6E8842@TYZPR06MB5275.apcprd06.prod.outlook.com>

Hi Yangtao,

On Fri, 2025-04-25 at 10:17 +0000, 李扬韬 wrote:
> Hi Slava,
> 
> > So, we need at first to check these issues. And it's a lot of work. :)
> 
> That's a lot of test failures, probably many for the same reason.
> 

Probably, yes, but we need to check it. If it is one or several root causes,
then we are lucky. :)

> Are there any changes to xfstest? Has this been sent to the fstest mailing list?
> 

This is a generic test cases and other file systems can pass it. For example, I
can pass xfstests for CephFS kernel client. So, we must think now that it is
HFS/HFS+ issues until we can prove the opposite one.

> I'm also planning to start deploying a local xfstest environment. : )
> 

Sounds great! I think we will need to distribute test-cases check to avoid the
duplication of efforts.

Thanks,
Slava.


      parent reply	other threads:[~2025-04-25 18:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 21:52 HFS/HFS+ maintainership action items Viacheslav Dubeyko
2025-04-22  2:43 ` Theodore Ts'o
2025-04-22  4:16   ` Darrick J. Wong
2025-04-22  7:21     ` John Paul Adrian Glaubitz
2025-04-22  7:20   ` John Paul Adrian Glaubitz
2025-04-22 12:35 ` John Paul Adrian Glaubitz
2025-04-22 21:12   ` Viacheslav Dubeyko
2025-04-22 21:47     ` John Paul Adrian Glaubitz
2025-04-22 21:48       ` John Paul Adrian Glaubitz
2025-04-25  1:06         ` Viacheslav Dubeyko
2025-04-25 10:17           ` 回复: " 李扬韬
2025-04-25 11:32             ` John Paul Adrian Glaubitz
2025-04-25 11:39               ` 回复: " 李扬韬
2025-04-25 18:25                 ` Viacheslav Dubeyko
2025-04-25 19:36                   ` 回复: " 李扬韬
2025-04-25 19:44                     ` Viacheslav Dubeyko
2025-04-26  6:17                       ` 回复: " 李扬韬
2025-04-26  6:59                         ` John Paul Adrian Glaubitz
2025-04-27 20:28                         ` Viacheslav Dubeyko
2025-05-02  3:01                           ` Theodore Ts'o
2025-05-02 19:14                             ` Viacheslav Dubeyko
2025-05-03  5:39                               ` Theodore Ts'o
2025-05-05 23:08                                 ` Viacheslav Dubeyko
2025-04-25 20:51                     ` John Paul Adrian Glaubitz
2025-04-25 18:02             ` Viacheslav Dubeyko [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=a5560fe32b5869a029891599f2e2d4b9e3d02a6d.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=brauner@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.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).