linux-kernel - Re: module: When modifying a module's text ignore modules which are going away too

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161123183344.ltp6w3wps4feei7g@jeyu>
Date:   Wed, 23 Nov 2016 10:33:44 -0800
From:   Jessica Yu <jeyu@...hat.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Aaron Tomlin <atomlin@...hat.com>, linux-kernel@...r.kernel.org,
        rusty@...tcorp.com.au
Subject: Re: module: When modifying a module's text ignore modules which are
 going away too

+++ Steven Rostedt [23/11/16 11:00 -0500]:
>On Wed, 9 Nov 2016 05:40:58 -0500
>Jessica Yu <jeyu@...hat.com> wrote:
>
>> +++ Aaron Tomlin [07/11/16 11:46 +0000]:
>> >Hi Jessica,
>> >
>> >Any thoughts?
>>
>> Hi Aaron,
>>
>> Thanks for your patience as I slowly work through a large swath of emails :-)
>>
>> Anyway, this looks fine to me. A going module's text should be (or
>> soon will be) rw anyway, so checking for going modules in the ro
>> case should be enough.
>>
>> Rusty, if you give your ack for the second patch, I can apply both
>> patches to my modules-next branch. I'll also incorporate Steven's
>> suggestion for a comment explaining why going modules shouldn't be
>> converted to ro in this context.
>>
>
>Hi Jessica,
>
>Have you pulled these in? I haven't noticed them in linux-next.

I currently have this queued up for 4.10. I'm still clearing up some
(unrelated to this patch) maintainership transition questions, but
expect the new modules tree to be pushed out and included in -next
by this week.

Thanks,
Jessica