From: Scott Mayhew <smayhew@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH 5/6] fstests: add an option for testing on CIFS
Date: Tue, 16 Apr 2024 17:56:28 -0400 [thread overview]
Message-ID: <Zh70DHtRSPo714No@aion> (raw)
In-Reply-To: <ZhmquRPIRkC1-dch@bombadil.infradead.org>
On Fri, 12 Apr 2024, Luis Chamberlain wrote:
> On Fri, Apr 12, 2024 at 04:49:59PM -0400, Scott Mayhew wrote:
> > Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> > ---
> > diff --git a/workflows/fstests/Kconfig b/workflows/fstests/Kconfig
> > index c797b24..e6664bf 100644
> > --- a/workflows/fstests/Kconfig
> > +++ b/workflows/fstests/Kconfig
> > diff --git a/workflows/fstests/cifs/Kconfig b/workflows/fstests/cifs/Kconfig
> > new file mode 100644
> > index 0000000..b88d1fe
> > --- /dev/null
> > +++ b/workflows/fstests/cifs/Kconfig
> > @@ -0,0 +1,75 @@
> > +config FSTESTS_SMB_SERVER_HOST
> > + string "Test Server hostname"
> > + default ""
> > + depends on !FSTESTS_USE_KDEVOPS_SMBD
> > + help
> > + The SMB server hostname or address to test against. Note that
> > + the clients will expect that an appropriate hierarchy is already
> > + created for them to mount and use.
> > + FIXME: document how to make that.
> > +
> > +# Distributions actively maintaining btrfs support should select this and then
>
> btrfs / CIFS
>
> > +if FSTESTS_CIFS_MANUAL_COVERAGE
> > +
> > +config FSTESTS_CIFS_SECTION_SMB3
> > + bool "Enable testing section: smb3"
> > + default y
> > + help
> > + Enabling this will test SMB3.
> > +
> > +config FSTESTS_CIFS_SECTION_SMB3_SEAL
> > + bool "Enable testing section: smb3_seal"
> > + default n
> > + help
> > + Enabling this will test SMB3 with encryption.
> > +
> > +config FSTESTS_CIFS_SECTION_SMB3_SIGN
> > + bool "Enable testing section: smb3_sign"
> > + default n
> > + help
> > + Enabling this will test SMB3 with signing.
> > +
> > +endif # FSTESTS_CIFS_MANUAL_COVERAGE
> > +
> > +if !FSTESTS_CIFS_MANUAL_COVERAGE
> > +
> > +config FSTESTS_CIFS_SECTION_SMB3
> > + bool
> > + default y
>
> I think you're just missing here the defaults for:
>
> * SMB3_SEAL
> * SMB3_SIGN
>
> Otherwise looks good.
Thanks, I've fixed both items. I'll wait for Chuck to push his nfstest
stuff and rebase on top of that to make sure there are no conflicts.
-Scott
>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
>
> Luis
>
next prev parent reply other threads:[~2024-04-16 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 20:49 [PATCH 0/6] Add an option for running fstests on CIFS Scott Mayhew
2024-04-12 20:49 ` [PATCH 1/6] oscheck.sh: add some special cases for cifs Scott Mayhew
2024-04-12 20:49 ` [PATCH 2/6] gendisks.sh: add special case " Scott Mayhew
2024-04-12 20:49 ` [PATCH 3/6] bringup: add a playbook to bring up an SMB server Scott Mayhew
2024-04-12 20:49 ` [PATCH 4/6] playbooks: add a playbook to create smb shares Scott Mayhew
2024-04-12 20:49 ` [PATCH 5/6] fstests: add an option for testing on CIFS Scott Mayhew
2024-04-12 21:42 ` Luis Chamberlain
2024-04-16 21:56 ` Scott Mayhew [this message]
2024-04-17 13:50 ` Chuck Lever III
2024-04-12 20:50 ` [PATCH 6/6] fstests: add expunges for cifs Scott Mayhew
2024-04-12 20:52 ` [PATCH 0/6] Add an option for running fstests on CIFS Chuck Lever III
2024-04-16 21:54 ` Scott Mayhew
2024-04-12 21:46 ` Luis Chamberlain
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=Zh70DHtRSPo714No@aion \
--to=smayhew@redhat.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
/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