From: Jessica Yu <jeyu@kernel.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Barret Rhoden <brho@google.com>,
linux-kernel@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
David Arcari <darcari@redhat.com>
Subject: Re: [PATCH] modules: fix livelock in add_unformed_module()
Date: Tue, 28 May 2019 16:47:02 +0200 [thread overview]
Message-ID: <20190528144702.GA3459@linux-8ccs> (raw)
In-Reply-To: <e5f7f37b-5c99-f9de-61ce-5b3394caf0d2@redhat.com>
+++ Prarit Bhargava [28/05/19 10:30 -0400]:
>
>
>On 5/22/19 1:08 PM, Prarit Bhargava wrote:
>>
>>
>> On 5/13/19 10:37 AM, Barret Rhoden wrote:
>>> Hi -
>>>
>>
>> Hey Barret, my apologies for not getting back to you earlier. I got caught up
>> in something that took me away from this issue.
>>
>>> On 5/13/19 7:23 AM, Prarit Bhargava wrote:
>>> [snip]
>>>> A module is loaded once for each cpu.
>>>
>>> Does one CPU succeed in loading the module, and the others fail with EEXIST?
>>>
>>>> My follow-up patch changes from wait_event_interruptible() to
>>>> wait_event_interruptible_timeout() so the CPUs are no longer sleeping and can
>>>> make progress on other tasks, which changes the return values from
>>>> wait_event_interruptible().
>>>>
>>>> https://marc.info/?l=linux-kernel&m=155724085927589&w=2
>>>>
>>>> I believe this also takes your concern into account?
>>>
>>> That patch might work for me, but I think it papers over the bug where the check
>>> on old->state that you make before sleeping (was COMING || UNFORMED, now !LIVE)
>>> doesn't match the check to wake up in finished_loading().
>>>
>>> The reason the issue might not show up in practice is that your patch basically
>>> polls, so the condition checks in finished_loading() are only a quicker exit.
>>>
>>> If you squash my patch into yours, I think it will cover that case. Though if
>>> polling is the right answer here, it also raises the question of whether or not
>>> we even need finished_loading().
>>>
>>
>> The more I look at this I think you're right. Let me do some additional testing
>> with your patch + my original patch.
>>
>
>I have done testing on arm64, s390x, ppc64le, ppc64, and x86 and have not seen
>any issues.
>
>Jessica, how would you like me to proceed? Would you like an updated patch with
>Signed-off's from both Barret & myself?
Hi Prarit,
A freshly sent patch with the squashed changes and Signed-off's would
be great. Thank you both for testing and looking into this!
Jessica
prev parent reply other threads:[~2019-05-28 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 22:22 [PATCH v3] kernel/module: Reschedule while waiting for modules to finish loading Prarit Bhargava
2019-05-01 7:49 ` Jessica Yu
2019-05-01 21:26 ` Prarit Bhargava
2019-05-02 9:48 ` Jessica Yu
2019-05-02 12:41 ` Prarit Bhargava
2019-05-02 17:46 ` Prarit Bhargava
2019-05-10 18:40 ` Barret Rhoden
2019-05-10 18:42 ` [PATCH] modules: fix livelock in add_unformed_module() Barret Rhoden
2019-05-13 11:23 ` Prarit Bhargava
2019-05-13 14:37 ` Barret Rhoden
2019-05-22 17:08 ` Prarit Bhargava
2019-05-28 14:30 ` Prarit Bhargava
2019-05-28 14:47 ` 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=20190528144702.GA3459@linux-8ccs \
--to=jeyu@kernel.org \
--cc=brho@google.com \
--cc=darcari@redhat.com \
--cc=heiko.carstens@de.ibm.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;
as well as URLs for NNTP newsgroup(s).