From: Petr Pavlu <petr.pavlu@suse.com>
To: mcgrof@kernel.org
Cc: pmladek@suse.com, david@redhat.com,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH v3 0/4] module: Merge same-name module load requests
Date: Sun, 16 Oct 2022 14:30:27 +0200 [thread overview]
Message-ID: <20221016123031.3963-1-petr.pavlu@suse.com> (raw)
Changes since v2 [1]:
- Add kselftests to verify the expected behavior.
- Split a clean-up change to the module_mutex comment into a separate patch.
- Clarify a description of the main patch and mention that it fixes also
a recently reported problem with module vmap space allocation errors.
- Improve some code comments.
Changes since v1 [2]:
- Change the error returned by a duplicate load when the main insert
fails from -ENODEV to -EBUSY.
- Change the error returned by a duplicate load when a same-name module
is going from -EAGAIN to -EBUSY.
- Use a per-shared_load_info completion object to inform waiting loads
when the main one is done.
- Add a patch to correct wake up of module_wq.
[1] https://lore.kernel.org/linux-modules/20220919123233.8538-1-petr.pavlu@suse.com/
[2] https://lore.kernel.org/linux-modules/20220905084131.14567-1-petr.pavlu@suse.com/
Petr Pavlu (4):
module: Correct wake up of module_wq
module: Update a comment describing what is protected by module_mutex
module: Merge same-name module load requests
selftests: kmod: Add tests for merging same-name module load requests
kernel/module/main.c | 222 +++++++++++++-----
tools/testing/selftests/kmod/.gitignore | 1 +
tools/testing/selftests/kmod/Makefile | 17 +-
tools/testing/selftests/kmod/init_module.c | 49 ++++
tools/testing/selftests/kmod/kmod.sh | 139 +++++++++++
.../selftests/kmod/kmod_test_0014/Makefile | 14 ++
.../kmod/kmod_test_0014/kmod_test_0014.c | 29 +++
7 files changed, 402 insertions(+), 69 deletions(-)
create mode 100644 tools/testing/selftests/kmod/.gitignore
create mode 100644 tools/testing/selftests/kmod/init_module.c
create mode 100644 tools/testing/selftests/kmod/kmod_test_0014/Makefile
create mode 100644 tools/testing/selftests/kmod/kmod_test_0014/kmod_test_0014.c
--
2.35.3
next reply other threads:[~2022-10-16 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 12:30 Petr Pavlu [this message]
2022-10-16 12:30 ` [PATCH v3 1/4] module: Correct wake up of module_wq Petr Pavlu
2022-10-17 7:26 ` David Hildenbrand
2022-10-16 12:30 ` [PATCH v3 2/4] module: Update a comment describing what is protected by module_mutex Petr Pavlu
2022-10-17 7:27 ` David Hildenbrand
2022-10-17 12:22 ` Petr Mladek
2022-10-16 12:30 ` [PATCH v3 3/4] module: Merge same-name module load requests Petr Pavlu
2022-10-17 7:43 ` David Hildenbrand
2022-10-18 8:52 ` Petr Pavlu
2022-10-18 9:18 ` David Hildenbrand
2022-10-17 12:54 ` Petr Mladek
2022-10-16 12:30 ` [PATCH v3 4/4] selftests: kmod: Add tests for merging " Petr Pavlu
2022-10-17 13:51 ` Petr Mladek
2023-01-12 9:03 ` Petr Pavlu
2023-01-13 14:45 ` Petr Mladek
2022-10-25 17:51 ` Luis Chamberlain
2022-10-25 23:01 ` 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=20221016123031.3963-1-petr.pavlu@suse.com \
--to=petr.pavlu@suse.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=pmladek@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