From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] No more module removal -- Unconference track
Date: Wed, 27 Aug 2014 15:43:23 +0900 [thread overview]
Message-ID: <53FD7E0B.7030806@hitachi.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1408262344310.2992@pobox.suse.cz>
(2014/08/27 6:45), Jiri Kosina wrote:
> On Tue, 26 Aug 2014, David Howells wrote:
>
>>> What I found is that the module unloading involving 2 stop_machine()s
>>> for each module removing. It must not be needed.
>>
>> IIRC, at least one of the stop_machine() calls was to prevent problems between
>> module removal oopsing and the symbol lookup trying to look up whilst dumping
>> the oops.
>
> This would be solved if symbol lookup would be RCU-ized though.
>
Yes, I did that :)
https://lkml.org/lkml/2014/8/25/143
https://lkml.org/lkml/2014/8/25/144
https://lkml.org/lkml/2014/8/25/145
Thank you,
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2014-08-27 6:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 14:48 Theodore Ts'o
2014-08-19 14:55 ` Guenter Roeck
2014-08-19 15:23 ` Theodore Ts'o
2014-08-19 15:40 ` Dan Carpenter
2014-08-19 15:47 ` Guenter Roeck
2014-08-19 16:09 ` Dan Carpenter
2014-08-19 16:34 ` Martin K. Petersen
2014-08-19 16:59 ` Rik van Riel
2014-08-19 17:19 ` Guenter Roeck
2014-08-19 16:43 ` David Woodhouse
2014-08-19 17:13 ` Grant Likely
2014-08-19 17:23 ` David Woodhouse
2014-08-19 15:54 ` Takashi Iwai
2014-08-25 11:01 ` Masami Hiramatsu
2014-08-25 11:05 ` Jiri Kosina
2014-08-26 5:24 ` Masami Hiramatsu
2014-08-27 23:05 ` Theodore Ts'o
2014-08-26 21:39 ` David Howells
2014-08-26 21:45 ` Jiri Kosina
2014-08-27 6:43 ` Masami Hiramatsu [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=53FD7E0B.7030806@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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