From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Martin Doucha <martin.doucha@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] ftp01.sh: Add support for test lftp
Date: Wed, 16 Oct 2024 15:48:48 +0200 [thread overview]
Message-ID: <20241016134848.GA88404@pevik> (raw)
In-Reply-To: <Zw-15cE2R0_5FOmJ@yuki.lan>
> Hi!
> > To be honest, I would rather to remove this FTP test because FTP protocol is
> > legacy. I know it is supposed to be a smoke test, but maybe using modern tools
> > would be better than keeping test working among various old FTP implementations.
> > (Also nontrivial setup is required just for few FTP tests:
> > https://github.com/linux-test-project/ltp/tree/master/testcases/network )
> > But probably Cyril would be against. @Cyril @Martin WDYT?
First, there are 7 FTP related tests:
testcases/network/tcp_cmds/ftp/ftp01.sh
testcases/network/stress/ftp/ftp-upload-stress02-rmt.sh
testcases/network/stress/ftp/ftp-upload-stress01-rmt.sh
testcases/network/stress/ftp/ftp-upload-stress.sh
testcases/network/stress/ftp/ftp-download-stress02-rmt.sh
testcases/network/stress/ftp/ftp-download-stress01-rmt.sh
testcases/network/stress/ftp/ftp-download-stress.sh
rmt files are using in ftp-upload-stress.sh and ftp-download-stress.sh. They are
part of runtest/net_stress.appl. Others tools/protocols for testing are SSH and DNS,
I wonder if we should get rid of whole tests in runtest/net_stress.appl.
Only ftp01.sh is converted to the new API, the rest is using the legacy API.
While it wouldn't be difficult to convert them, I wonder if it's really useful
for modern kernel testing. Is it really worth to have these tests as a smoke
tests?
> So where is the ftp server setup code? Or do we expect ftp server to be
> installed and configured prior to the test execution?
ftp-download-stress.sh and ftp-upload-stress.sh have some vsftpd server setup.
Here is a description of some of the tests:
ftp-download-stress01
Verify the ftp server or the kernel is not down after a ftp client
requests large data via IPv4/IPv6
ftp-download-stress02
Verify the ftp server or the kernel is not down after many ftp
clients request data over IPv4/IPv6 asynchronously for a long time
ftp-upload-stress01
Verify the ftp server or the kernel is not down after a ftp client
uploads a large data via IPv4/IPv6
ftp-upload-stress02
Verify the ftp server or the kernel is not down after many ftp clients
uploads data over IPv4/IPv6 asynchronously for a long time
I doubt that FTP server would crash the kernel, IMHO it's more about testing the
FTP server itself.
Kind regards,
Petr
> The actuall test does not look that complex to me.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-10-16 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 10:03 [LTP] [PATCH v1] tst_test.sh: Add support for localhost ssh key setup Wei Gao via ltp
2024-09-18 11:46 ` Martin Doucha
2024-09-24 10:15 ` Wei Gao via ltp
2024-09-24 12:08 ` Martin Doucha
2024-09-25 3:57 ` [LTP] [PATCH v2] ftp01.sh: Add support for test lftp Wei Gao via ltp
2024-10-15 19:39 ` Petr Vorel
2024-10-16 3:13 ` Wei Gao via ltp
2024-10-16 13:41 ` Petr Vorel
2024-11-04 16:20 ` Petr Vorel
2024-10-16 12:47 ` Cyril Hrubis
2024-10-16 13:48 ` Petr Vorel [this message]
2024-10-16 15:32 ` Cyril Hrubis
2024-10-16 16:17 ` Martin Doucha
2024-10-16 21:15 ` Petr Vorel
2024-11-01 12:11 ` Cyril Hrubis
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=20241016134848.GA88404@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.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