All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Tom Talpey <tom@talpey.com>, linux-cifs@vger.kernel.org
Subject: Re: SMB client testing wiki
Date: Fri, 26 Aug 2022 14:10:46 -0300	[thread overview]
Message-ID: <87zgfr2and.fsf@cjr.nz> (raw)
In-Reply-To: <165e9b10-2f3e-dc88-029a-c8157a98f095@talpey.com>

Tom Talpey <tom@talpey.com> writes:

>
> On 8/26/2022 12:01 PM, Paulo Alcantara wrote:
>> Tom Talpey <tom@talpey.com> writes:
>> 
>>> Easy enough! How do I know if it "passes" though? My understanding
>>> is that a bunch of tests are expected to fail, or at least warn.
>>> Do I need to test a clean client, then compare results? Or am I
>>> misunderstanding, and FSTYP=cifs is taking care of it?
>> 
>> That's a really good question.  We have a pre-defined list of tests that
>> get run by a specfic SMB version, server, if multichannel, etc.
>
> Yeah, there are a few exclusion files on the wiki, but they look
> really old. Also, I cannot believe that "vers=3.0" is the proper
> default, as linked there!!!

Yeah :-(  We should definitely update it.

>> Steve might send you the list of pre-defined tests that get run on our
>> buildbot so you can try it out.  He usually keeps those lists
>> up-to-date.
>
> The buildbot doesn't do RDMA, or I'd consider that. But it's a lot
> more convenient to have a local harness either way.

It currently doesn't, unfortunately.  You could at least get the same
set of tests that run over 3.1.1 against samba and/or ksmbd and then
change mount options to get RDMA enabled.  And of course, let us know
when you get it working and let's add it to our buildbot as well ;-)

  reply	other threads:[~2022-08-26 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 14:05 SMB client testing wiki Tom Talpey
2022-08-26 14:53 ` Paulo Alcantara
2022-08-26 15:11   ` Tom Talpey
2022-08-26 16:01     ` Paulo Alcantara
2022-08-26 16:56       ` Tom Talpey
2022-08-26 17:10         ` Paulo Alcantara [this message]
     [not found]   ` <CAH2r5msqW0RnNxETt=2Ec3Eq3o+RFgR+bQB6DFoCvBaNE2Hx4A@mail.gmail.com>
2022-08-26 15:25     ` Tom Talpey

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=87zgfr2and.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=linux-cifs@vger.kernel.org \
    --cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.