From: Jessica Yu <jeyu@kernel.org>
To: Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
Barret Rhoden <brho@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
linux-kernel@vger.kernel.org, David Arcari <darcari@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 1/1] kernel/module.c: wakeup processes in module_wq on module unload
Date: Fri, 15 Nov 2019 11:28:33 +0100 [thread overview]
Message-ID: <20191115102832.GA1647@linux-8ccs> (raw)
In-Reply-To: <20191113092950.15556-2-khorenko@virtuozzo.com>
+++ Konstantin Khorenko [13/11/19 12:29 +0300]:
>Fix the race between load and unload a kernel module.
>
>sys_delete_module()
> try_stop_module()
> mod->state = _GOING
> add_unformed_module()
> old = find_module_all()
> (old->state == _GOING =>
> wait_event_interruptible())
>
> During pre-condition
> finished_loading() rets 0
> schedule()
> (never gets waken up later)
> free_module()
> mod->state = _UNFORMED
> list_del_rcu(&mod->list)
> (dels mod from "modules" list)
>
>return
>
>The race above leads to modprobe hanging forever on loading
>a module.
>
>Error paths on loading module call wake_up_all(&module_wq) after
>freeing module, so let's do the same on straight module unload.
>
>Fixes: 6e6de3dee51a ("kernel/module.c: Only return -EEXIST
>for modules that have finished loading")
>
>Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
Thanks Konstantin for catching this. I've applied this to
modules-next.
Jessica
prev parent reply other threads:[~2019-11-15 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:29 [PATCH 0/1] kernel/module.c: don't allow modprobe to hang forever on a module load Konstantin Khorenko
2019-11-13 9:29 ` [PATCH 1/1] kernel/module.c: wakeup processes in module_wq on module unload Konstantin Khorenko
2019-11-13 13:51 ` Prarit Bhargava
2019-11-15 10:28 ` Jessica Yu [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=20191115102832.GA1647@linux-8ccs \
--to=jeyu@kernel.org \
--cc=aryabinin@virtuozzo.com \
--cc=brho@google.com \
--cc=darcari@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=khorenko@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.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