From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
patches@lists.linux.dev, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org, pmladek@suse.com, david@redhat.com,
petr.pavlu@suse.com, prarit@redhat.com
Cc: christophe.leroy@csgroup.eu, song@kernel.org, dave@stgolabs.net,
a.manzanares@samsung.com, fan.ni@samsung.com,
vincent.fu@samsung.com
Subject: Re: [PATCH v3] stress-module: stress finit_module() and delete_module()
Date: Wed, 22 Mar 2023 18:11:50 +0000 [thread overview]
Message-ID: <bf1c475c-b98c-7381-33c0-602c2ab6349a@gmail.com> (raw)
In-Reply-To: <ZBtDSh6f+rWqFLtC@bombadil.infradead.org>
On 22/03/2023 18:04, Luis Chamberlain wrote:
> On Tue, Mar 21, 2023 at 08:23:50PM -0700, Luis Chamberlain wrote:
>> Example uses:
>>
>> sudo ./stress-ng --module 1 --module-name xfs
>> sudo ./stress-ng --module 1 --module-name xfs --module-sharedfd
>
> The use case with --module 8192 was causing some errors from
> stress-ng having unexpected bail out messages before ramp up.
>
>> diff --git a/stress-module.c b/stress-module.c
>> new file mode 100644
>> index 00000000..cee581bd
>> --- /dev/null
>> +++ b/stress-module.c
>> + //snprintf(module_path, strlen(module_path), "%s/%s/%s",
>> + snprintf(module_path, PATH_MAX*2, "%s/%s/%s",
>> + dirname_default_prefix,
>> + u.release, module);
>> + ret = 0;
>
> I forgot to remove this stray comment.
No worries, I can fix that up when I apply the patch.
>
>> + /*
>> + * We're not stressing the modules.dep --> module path lookup,
>> + * just the finit_module() calls and so only do the lookup once.
>> + */
>> + if (args->instance != 0) {
>> + if (!module_path_found)
>> + return EXIT_SUCCESS;
>> + }
>
> So here was the reason for the complaints, Although changing this to
> return just EXIT_NO_RESOURCE cures the warning, I don't think the
> non instance 0 workers are doing anything then. Is that right Colin?
I'll have a look at that when I test this out later tonight.
>
> Luis
prev parent reply other threads:[~2023-03-22 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 3:23 Luis Chamberlain
2023-03-22 18:04 ` Luis Chamberlain
2023-03-22 18:11 ` Colin King (gmail) [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=bf1c475c-b98c-7381-33c0-602c2ab6349a@gmail.com \
--to=colin.i.king@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=fan.ni@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=patches@lists.linux.dev \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=song@kernel.org \
--cc=vincent.fu@samsung.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
all inboxes | Powered by JetHome®