Linux-CIFS Archive mirror
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	 samba-technical <samba-technical@lists.samba.org>
Subject: Re: current ksmbd
Date: Tue, 16 Apr 2024 09:28:42 +0900	[thread overview]
Message-ID: <CAKYAXd-gN2uQ4B9UvUdvCM_A+qnrMuCHGQO7irfFozbjKBxpZA@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5ms7EWvNFVJ7_D7QXWOyj+oViKDJD2EuoY3n=w1c5wLTKQ@mail.gmail.com>

2024년 4월 16일 (화) 오전 1:54, Steve French <smfrench@gmail.com>님이 작성:
>
> We are up to 221 fstests run vs. ksmbd, and buildbot tests pass with
> current ksmb (this is with 6.9-rc4):
> http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/10/builds/52
>
> There are lots of minor features (and some fixes) that should be able
> to be doable to increase this number even more.
>
> Note that Samba passes some tests that are skipped when run to ksmbd
> that should be investigated:
> e.g. generic/022 ("xfs_io fcollapse") and generic/351 ("xfs_io
> fsinsert") and also generic/021 and 031 ("fallocate: Invalid argument)
> and generic/525 ("pread: invalid argument") and generic/568 (which
> looks like fallocate bug)
Okay. I will check it after sambaXP.

Thanks for your check!
>
> Samba fails two tests that pass to ksmbd generic/286 ("create sparse
> file failed") and generic/591 (splice test) that also should be
> investigated.
>
>
> --
> Thanks,
>
> Steve

      reply	other threads:[~2024-04-16  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 16:54 current ksmbd Steve French
2024-04-16  0:28 ` Namjae Jeon [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=CAKYAXd-gN2uQ4B9UvUdvCM_A+qnrMuCHGQO7irfFozbjKBxpZA@mail.gmail.com \
    --to=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=samba-technical@lists.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).